Skip to main content
Glama

Measured speed and reliability

measured_performance
Read-onlyIdempotent

What hourly test requests measured per model and channel: time to first token, output speed, share of requests answered, and whether the charge matched the list price. Optional model and channel. Measured by AuraMatrix from one server in Los Angeles with one small request per model per hour; a sample, not a benchmark or a service-level figure. Requests our own account was refused are left out.

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": "measured_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoModel id or alias; omit for all models, fastest first
channelNoChannel id, e.g. openrouter, anthropic-api

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the measurement methodology (one Los Angeles server, one small request per model per hour), the sampling limitation, and an explicit exclusion rule for refused requests. These are exactly the interpretation caveats an agent needs before citing the numbers.

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?

Three sentences, front-loaded with the returned metrics, followed by scope and then caveats - no filler. The opening clause 'What hourly test requests measured per model and channel' is slightly awkward grammatically, which keeps it off a 5.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by naming the metric fields returned, and it covers the read-only, non-destructive nature transitively through annotations. It does not say whether results come back as hourly rows or per-model aggregates, a minor remaining gap for a data-retrieval tool.

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

Parameters3/5

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

Schema coverage is 100% and the schema already explains 'omit for all models, fastest first' and gives a channel id example, so the description's single line 'Optional model and channel' adds nothing beyond it. Baseline 3 is correct when the schema does the heavy lifting.

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 enumerates exactly what is returned: time to first token, output speed, share of requests answered, and charge-vs-list-price, scoped per model and channel. That is specific enough to separate it from pricing siblings such as cheapest or compare_channels, though the retrieval verb itself is only implied ('What hourly test requests measured...').

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?

It states both parameters are optional and adds an important usage caveat that the data is 'a sample, not a benchmark or a service-level figure', which tells the agent how far to trust the numbers. It stops short of routing guidance - there is no explicit statement of when to prefer this over compare_channels or cheapest, so the agent must infer the choice.

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.