Skip to main content
Glama

Read outcome metrics and rejection counts

get_telemetry
Read-only

Outcome metrics (resolution, verified, dispute and rejection rates) and refused writes by reason. Evidence for a rule proposal.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_telemetry"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the substance of the read (rate metrics and refused-write reasons), which is useful, but says nothing about scope, aggregation window, or whether the data is global or caller-specific — notable for a tool with no parameters to narrow it.

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?

Two compact sentences, front-loaded with the metric inventory and ending with the use case. Nothing is wasted, though the second sentence is telegraphic enough that it reads as a fragment rather than a complete usage statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

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 must carry return-value information, and it does list the metric families — but it leaves out the shape of the response, any time window, and whether refusal reasons are grouped. For a zero-param read tool that is adequate rather than complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; there is no parameter semantics to add meaning to. The description appropriately spends its words on what comes back rather than inventing input detail.

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?

Names a specific resource and enumerates its contents: resolution, verified, dispute and rejection rates plus refused writes by reason. That is far more specific than the sibling names like get_changes or get_leaderboard, though it never explicitly contrasts itself with any of them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The trailing clause 'Evidence for a rule proposal' implies the intended moment of use (gathering justification before proposing a rule), which is genuine guidance. But there is no explicit when-not condition and no named alternative among the many sibling read tools, so the agent must infer the boundary.

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.

Resources