Skip to main content
Glama

Measure possible savings

measure_traffic
Read-onlyIdempotent

Measure how much of your own agent traffic could be saved. NO ACCOUNT OR KEY NEEDED — use this first. Returns byte savings over the wire and, if a query is given, token savings from selective context retrieval. Nothing is stored: the text is compressed in memory and discarded. Rate limited to 20 calls per hour per IP.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "texts": "<texts>"
    },
    "name": "measure_traffic"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional. What your agent would search its memory for. Given this, token savings are measured too.
textsYesYour actual messages. 200 max.
dict_idNoWhich trained dictionary to measure against. Call list_packages to see the options and their measured figures.finance

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses privacy behavior ('nothing is stored: the text is compressed in memory and discarded') and a concrete rate limit (20 calls/hour/IP), which are exactly the operational facts an agent needs. It stops short of saying what a throttled call looks like on failure, but the added value over annotations is substantial.

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?

Four short sentences, front-loaded with the value proposition and the no-key note. Every sentence carries a distinct fact (purpose, returns, privacy, rate limit) with no filler; it is close to optimally sized, though the em-dash clause is slightly dense.

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 must characterize the return, and it does so at a high level (byte savings over the wire, token savings when a query is supplied). Combined with privacy and rate-limit disclosures and full schema coverage, an agent can call this correctly, though the exact response shape is left implicit.

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 description coverage is 100%, so all three parameters are already documented in the schema, including the query-conditional token measurement and the 200-item cap. The description adds no syntax, format, or sizing guidance beyond what the schema states, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Measure how much of your own agent traffic could be saved') and immediately names what the tool returns: byte savings over the wire and, conditionally, token savings. It also positions the tool against siblings with 'NO ACCOUNT OR KEY NEEDED — use this first,' so an agent can tell this is the free pre-flight estimator rather than assemble_context or pack_batch.

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

Usage Guidelines4/5

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

'use this first' gives explicit ordering guidance, and the no-account/no-key note tells the agent this is the entry point before tools that require a key. The dict_id parameter description routes the agent to list_packages for options. There is no explicit statement of when NOT to use it (e.g., after real keys are issued), but the context is otherwise clear.

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.