Skip to main content
Glama

efficiency_report

Read-onlyIdempotent

Report ContextPro's persistent, auditable context-compression estimates by tool. History stores numeric metrics only—never prompts, source code, response bodies, or file paths. Token savings are estimates, not billing data.

Instructions

Report ContextPro's persistent, auditable context-compression estimates by tool. History stores numeric metrics only—never prompts, source code, response bodies, or file paths. Token savings are estimates, not billing data.

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

Input Schema

NameRequiredDescriptionDefault
rootNoAbsolute project root. Omit only where this session started; required elsewhere and on every subagent call.
scopeNoHistory window. Default: this MCP session. Call at task completion and quote finalSummary.
formatNoReturn plain text or JSON. Default: text.
history_limitNoMaximum recent saving events. Use 0 for totals only; default 10.
contextpro_cost_usdNoOptional known ContextPro operating cost for this window; deducted only when supplied. Never guess.
input_cost_per_millionNoOptional model input price in USD per million tokens. When provided, returns a clearly-labelled hypothetical cost estimate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.0
    • changedInput schema / properties / root / description
      Previous value: -"Absolute project root. Required with linked worktrees; subagents must pass their own worktree root on every call."New value: +"Absolute project root. Omit only where this session started; required elsewhere and on every subagent call."
  2. First observedv1.4.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, closed-world, non-destructive operation, so the safety bar is met. The description still adds real value beyond them: it discloses what the history does and does not retain (numeric metrics only, never prompts, code, response bodies, or file paths) and warns that savings are estimates rather than billing data — a caveat that directly affects how results should be reported.

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 short sentences, front-loaded with purpose and followed by the two caveats that matter most. Slightly dense phrasing ('persistent, auditable context-compression estimates') but nothing is padding.

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?

With six optional parameters and no output schema, the definition needs to describe what the report actually contains, but it never says what fields or sections a caller will get back (totals, per-tool events, cost figures). Privacy and estimate caveats are well covered, yet an agent still can't predict the response shape before calling.

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% across all six optional parameters, so the schema already carries per-parameter meaning, including the cost and hypothetical-pricing inputs. The description adds no parameter-level detail (nothing on root, scope windows, format, or history_limit), so the baseline of 3 applies.

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 verb and resource: report context-compression / token-savings estimates, broken down by tool, from a persistent history. That is clear enough to act on, but it never distinguishes this from look-alike siblings such as status, explain, or task_pack, which also surface session/project information.

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?

No when-to-use or when-not-to-use guidance appears in the description, and no alternative is named. The only timing instruction ('call at task completion and quote finalSummary') lives inside the scope parameter schema, so the description itself leaves invocation context to inference.

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