kinsta_analytics_top-asnsIdentify top autonomous systems (ASNs) for a Kinsta environment to analyze traffic sources. Specify environment ID and optional date range or time span.
Get top autonomous system numbers.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | Custom end date (YYYY-MM-DD) | |
| from | No | Custom start date (YYYY-MM-DD) | |
| env_id | Yes | The environment ID | |
| time_span | No |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds no further behavioral context such as what the response looks like, whether results are sorted, how many items are returned, or how the time range is applied. It neither contradicts annotations nor enriches them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, short sentence with no wasted words and the core action is front-loaded. However, it is under-specified for a tool with four parameters and many siblings, so the brevity comes at the cost of useful guidance.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, so the description carries the burden of explaining expected results, but it does not mention return format, sorting, limits, or how time parameters affect output. Given the tool's complexity—four parameters and many sibling analytics tools—the description is incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description provides no information about env_id, time_span, from, or to. The schema covers 75% of parameters with descriptions, but time_span only has an enum without an explicit description. Since schema coverage is below the 80% threshold, the description should have compensated, but it adds no parameter-level meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource: 'Get top autonomous system numbers,' which clearly differentiates this from sibling analytics top-* tools like top-countries, top-cities, and top-browsers. It also expands the acronym ASNs. However, it omits any context about the environment or time span, relying on the schema for those details.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives such as top-countries or top-host. No prerequisites, exclusions, or conditions are stated. The only implied usage is 'if you need top ASNs,' but the description does not help an agent choose among the many sibling analytics tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.