monte-carlo-data/mc-agent-toolkit / skills/account-analytics
monte-carlo-account-analytics
UnverifiedAnswers questions about your Monte Carlo account (alerts, data quality, coverage, monitors, credits, monitor runs) from the Analytics API, helps sharpen vague questions, and builds dashboards on request.
Account analytics
Answer questions about the user's own Monte Carlo account from the Analytics API. Every number comes from a request you ran; never estimate, never fill a gap from memory. The API serves only the account the Monte Carlo MCP server is connected to: never compare with, or answer for, other accounts.
Monte Carlo tool routing (required): Always call Monte Carlo MCP tools through this plugin's bundled server, whose fully-qualified tool names are
mcp__plugin_mc-agent-toolkit_monte-carlo-mcp__<tool>(e.g.mcp__plugin_mc-agent-toolkit_monte-carlo-mcp__query_account_analytics). Bare tool names used in this skill (get_account_analytics_docs,get_account_analytics_catalog,query_account_analytics,get_mc_webapp_url) refer to that bundled server. If the session also has a separately-configuredmonte-carlo-mcpserver, do not route to it — it may point at a different endpoint or credentials.
Tools
get_account_analytics_docs: withoutslug, the list of docs pages (slug, title, summary); withslug, that page as Markdown, as written.get_account_analytics_catalog: without arguments, every metric you can query (name, label, description); withmetrics, the dimensions all of them can be grouped and filtered by;searchkeeps the items whose name, label or description contains a text.query_account_analytics: runs one request (metrics,group_by,filters,order_by,limit) and returnscolumns,rows,data_as_ofandtruncated. A request the data cannot answer is refused with the reason and what works.get_mc_webapp_url: the address of the user's Monte Carlo instance (such ashttps://getmontecarlo.comorhttps://eu1.getmontecarlo.com), for links to items. Call it once, before the first answer that names items.
If get_account_analytics_catalog or query_account_analytics is not in the session, or either returns a 404, the
Analytics API is not enabled for this account: say so and stop. Do not retry, and do not work the numbers out from
other tools (get_alerts, get_monitors and the like): they count differently and would not match the Analytics API.
Docs
Read the Analytics API docs with get_account_analytics_docs: once without slug for the list of pages, then one call
per page you need. The pages:
| Page | Slug |
|---|---|
| Overview | analytics-api |
| How to query | analytics-api-querying |
| Data catalog (Metrics, Dimensions, Glossary) | analytics-api-data-catalog |
| Dashboard examples | analytics-api-dashboard-examples |
| Dashboard style | analytics-api-dashboard-style |
A link written doc:<slug> leads to another page: read it with that slug.
When get_account_analytics_docs is not in the session or fails, fetch the same pages from the Monte Carlo docs at
https://docs.getmontecarlo.com/docs/<slug>.md: the .md address returns the page as written, where the address
without it can come back summarised. When neither works, use get_account_analytics_catalog for names and
descriptions, and say that the topic rules could not be read.
Workflow
Follow references/core.md: find the business question, build the request, run and check, answer in the chat, and build a dashboard only when asked. The core is shared with an internal twin of this skill; keep anything specific to this skill here, not there.
Here a request runs as query_account_analytics; a request it refuses names what works. Use get_account_analytics_catalog to list
the metrics when the user asks what they can ask, and before you decline (core.md, section 3).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |