Skip to main content
Glama

get_token_savings_metrics

Retrieve cumulative token and cost savings analytics to track reductions in token usage and spending achieved by AI coding agents.

Instructions

Returns cumulative token and cost savings analytics.

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_token_savings_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.4

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure and does not meet it. It implies a read-only operation, but never states whether 'cumulative' means since session start, since install, or per-project, nor whether calling it has any side effects or cost. For a metrics tool the accumulation window is the single most important behavioral fact and it is undefined.

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 front-loaded sentence with no filler, which is appropriate for a no-argument tool. The terseness is efficient rather than under-specified in structure, though the one sentence does leave the scope of 'cumulative' unresolved.

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?

For a zero-parameter tool this is close to adequate, but there is no output schema, so the description is the only place an agent could learn what the metrics contain and over what period. It names the categories (token and cost savings) but not the accumulation window or return shape, leaving a real gap.

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 nothing the description needs to disambiguate. It correctly does not waste words describing nonexistent inputs.

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?

States a specific verb ('Returns') and resource ('cumulative token and cost savings analytics'), so the agent knows exactly what data comes back. It does not distinguish itself from any sibling, though none of the listed siblings appear to be competing analytics tools, so the ambiguity is minor.

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 at all: no mention of when an agent should call this versus other tools, no preconditions, and no indication of whether it should be polled or called once. The agent must infer usage entirely from the name.

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