Skip to main content
Glama

report

Read-onlyIdempotent

Calculate tokens and money saved by the current session, net of re-expansion, based on prompt caching and how many turns each output stays in context.

Instructions

Tokens saved in this session, net of anything re-expanded, and the money saved at EXAMPLE prices.

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

Input Schema

NameRequiredDescriptionDefault
cachedNoAssume prompt caching.
later_turnsNoHow many more turns each output stays in context.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world, so safety is covered. The description adds genuinely non-obvious context beyond that: savings are net of anything re-expanded, they are scoped to the current session, and the monetary figure is computed at 'EXAMPLE prices' — an important caveat that the returned cost numbers are illustrative, not billing-grade. It stops short of explaining how the two parameters affect the computation.

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?

A single sentence with the core concept front-loaded and no filler. The uppercase 'EXAMPLE prices' is slightly jarring stylistically but conveys a real caveat efficiently. Nothing is redundant.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. The description supplies the session scope and the pricing caveat, which are the two things an agent would otherwise misread. Only the absence of any usage/differentiation cue versus sibling tools keeps it from being complete.

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%, with both optional parameters fully documented in the schema ('Assume prompt caching', 'How many more turns each output stays in context'). The description adds no parameter-level meaning beyond that, though 'net of anything re-expanded' loosely relates to the later_turns parameter. Baseline 3 is appropriate when the schema carries the burden.

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 states a specific output: tokens saved this session (net of re-expansion) plus monetary savings, which clearly identifies this as a session-level savings report rather than a transformation. It does not explicitly contrast itself with the transform siblings (expand, trim_log, etc.), but the resource described is distinct enough that an agent can separate them. The generic name 'report' is rescued by the description's specificity.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when not to use it, and no reference to alternatives such as expand for re-expanding output. The phrase 'in this session' only hints that it is a cumulative check. An agent must infer that this is the tool to call to see accumulated savings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.