get_breakdown
Top-N breakdown of a site's traffic by one dimension.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | ||
| days | No | ||
| from | No | ||
| site | Yes | ||
| limit | No | ||
| dimension | Yes |
DevDome Analytics
by com.devdome
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.7/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavior itself, but it only states 'Top-N breakdown' and 'by one dimension'. It does not explain result shape, default limit, sorting, time-range handling, or edge cases.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a short, front-loaded sentence with no redundant wording. It is concise and scannable, though it achieves conciseness by omitting meaningful detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations, the description is too thin to fully support correct invocation. It does not explain the return payload, time-range parameters, limit behavior, or dimension-specific results, leaving too much to inference.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, yet the description only clarifies site, dimension, and the Top-N concept. It leaves to, from, days, and limit semantics to their parameter names without describing formats, defaults, or interactions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies a top-N traffic breakdown grouped by one dimension, naming both the operation and the resource. It is clear on its own but does not explicitly differentiate it from sibling analytics tools like get_stats or get_timeseries.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use get_breakdown versus the sibling tools. The word 'breakdown' implies a use case, but there are no conditions, exclusions, or alternative routing cues.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.6/5.0
Disambiguation5/5
Each tool targets a distinct resource or analytical view: site management (add/list/verify) is cleanly separated from analytics (stats, timeseries, visitors, realtime, bot report, breakdown, health). Even the traffic-related getters differ clearly by granularity and intent, so an agent is unlikely to confuse them.
Naming Consistency5/5
The naming follows a consistent verb_noun pattern: add_site, list_sites, verify_site, and all analytics tools use get_<noun>. This makes the toolset predictable and easy to navigate.
Tool Count5/5
Ten tools is well-scoped for an analytics product, covering both site administration and multiple data views without redundancy or bloat. Each tool earns its place in the API surface.
Completeness4/5
The core site lifecycle is covered (add, list, verify), and the analytics side is thorough with stats, timeseries, breakdown, realtime, visitors, bot reports, and health. Minor gaps exist, such as no remove/update site or deeper filtering options, but agents can complete typical workflows without dead ends.