Skip to content

monte-carlo-data/mc-agent-toolkit / skills/account-analytics

monte-carlo-account-analytics

Unverified

Answers 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.

FileKindSize
SKILL.mdskill md4.7 KB
references/core.mdmarkdown15.6 KB
---
name: monte-carlo-account-analytics
description: Answers 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.
when_to_use: |
  The user asks for numbers, lists, trends or a dashboard about their own Monte Carlo account: "how many alerts did we get last week", "which tables have no monitor", "which monitors are erroring and since when", "coverage per data product", "how many credits this quarter", "how is our data quality", "build a data quality dashboard". Not for investigating one alert (incident-response) or one table's health (asset-health).
bucket: Monitoring
---

# 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):** For Monte Carlo operations such as
> `get_account_analytics_docs`, `get_account_analytics_catalog`, `query_account_analytics` and
> `get_mc_webapp_url`, use the tool ID your client exposes on the connection for the intended
> account. Proceed when there is one suitable connection and no evidence of an account or source
> mismatch. If the choice is ambiguous, ask which connection to use before making a Monte Carlo
> call; if you can't get an answer, leave the call pending. Use the selected connection throughout.
> If it is unavailable or lacks the operation, follow this skill's fallback where it has one, or
> report what is missing.

<!-- plugin-only:start -->
> **With the Agent Toolkit plugin:** When using the toolkit plugin or its installer, prefer the
> connection it provides or configures (normally named `monte-carlo-mcp`) when it is suitable for the
> intended account. If you know that connection is missing, confirm the intended alternative before
> using another one.
<!-- plugin-only:end -->

## Tools

- **`get_account_analytics_docs`**: without `slug`, the list of docs pages (slug, title, summary); with `slug`, that
  page as Markdown, as written.
- **`get_account_analytics_catalog`**: without arguments, every metric you can query (name, label, description); with
  `metrics`, the dimensions all of them can be grouped and filtered by; `search` keeps the items whose name, label or description contains a text.
- **`query_account_analytics`**: runs one request (`metrics`, `group_by`, `filters`, `order_by`, `limit`) and returns `columns`,
  `rows`, `data_as_of` and `truncated`. 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 as `https://getmontecarlo.com` or
  `https://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](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).
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall