kinsta_analytics_disk-spaceRetrieve disk space usage analytics for any Kinsta environment using its ID and time zone, with custom date range options for detailed insights.
Get disk space analytics for an environment.
| 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 | ||
| time_zone | Yes |
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, which cover the safety profile. The description adds nothing beyond stating it retrieves analytics; it does not disclose behavior like time range handling, response format, or any limitations. Since annotations carry the load, the description's marginal value is low.
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, concise sentence with no filler. It is appropriately short, though it sacrifices substance for brevity, making it slightly under-specified but still efficient.
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?
With no output schema and five parameters, the description is severely incomplete. It does not explain what the returned analytics look like, how time ranges are applied, or the relationship between time_span and from/to. Given the complexity and the need to route among many sibling analytics tools, the description falls short of what an agent needs to call it correctly.
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?
Schema description coverage is 60%: to, from, and env_id have descriptions, but time_span and time_zone lack descriptions (only an enum and a pattern). The description provides no additional parameter context, so it does not compensate for the undocumented parameters. An agent would need to infer that time_span has predefined ranges and time_zone requires a specific offset format.
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 states a specific verb ('Get') and resource ('disk space analytics for an environment'), clearly distinguishing it from sibling analytics tools like bandwidth or visits. It does not explicitly name a sibling, but the resource is specific enough to avoid ambiguity.
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?
No guidance is given on when to use this tool versus other analytics tools, nor any mention of typical use cases or prerequisites. The description is purely declarative and does not help an agent decide between this and kinsta_analytics_bandwidth or kinsta_analytics_visits.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.