Retrieve agent telemetry metrics, rolling spend volume, and security events over a specified timeframe. Use this to monitor agent activity and detect anomalies.
Retrieve agent telemetry metrics, rolling spend volume, and security events.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max events to return (default: 20) | |
| timeframeHours | No | Timeframe in hours (default: 24) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It only states the action 'retrieve' and the data categories, but does not mention pagination, default limits, authentication requirements, whether data is a snapshot or continuous, or any potential side effects. This is a significant gap for a data-retrieval tool.
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, well-formed sentence with no wasted words. It is concise, though it could be slightly restructured to front-load the most critical information, but it is not verbose.
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?
Given there is no output schema and no annotations, the description should clarify return format, pagination behavior, and any prerequisites. None of this is provided. An agent calling this tool would not know what the response structure looks like or if there are any constraints beyond the parameters.
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 input schema has 100% description coverage for both parameters (limit and timeframeHours), including defaults. The tool description adds no extra meaning beyond what the schema already provides, so the baseline of 3 is appropriate.
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 clear verb ('Retrieve') and a specific resource ('agent telemetry metrics, rolling spend volume, and security events'), which distinguishes it from sibling tools like get_agent_identity and get_spending_guardrails. The purpose is unambiguous and directly actionable.
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 provided on when to use this tool versus alternatives, nor any exclusions or context for selection. While the name suggests telemetry retrieval, the description offers no explicit routing information to an agent deciding between this and related tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.