Skip to main content
Glama

Compute efficiency report

compute_efficiency_report
Read-onlyIdempotent

Free read: decision/outcome receipts, route modes, compute avoided, predicted savings, predicted-vs-observed cost/latency/energy coverage, and Landauer-floor context. Estimates and observations stay distinct.

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

Input Schema

NameRequiredDescriptionDefault
limitNoOptional. The most recent decisions to include. Default 50.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Optional. The most recent decisions to include. Default 50."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the call is free (no compute charged), and estimates versus observations are kept distinct, which warns the agent not to conflate predicted and observed figures.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the cost signal front-loaded, followed by a compact enumeration of the report's sections and one crucial caveat about estimates vs observations. No filler, and the most decision-relevant fact ('Free read') comes first.

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-value detail is unnecessary, and there is only one optional parameter that the schema already documents. What the description does provide — cost-free access and the estimate/observation distinction — covers the main risks; only explicit routing guidance against sibling tools is missing.

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% and the single 'limit' parameter is fully documented in the schema with a default of 50. The description adds no meaning about the limit or ordering, so the baseline 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 enumerates the concrete contents of the report — decision/outcome receipts, route modes, compute avoided, predicted savings, cost/latency/energy coverage, Landauer-floor context — so the agent knows exactly what resource it gets back. The verb is only implied by the name ('report'), and nothing distinguishes it from get_ledger or get_agent, so it falls short of a 5.

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?

'Free read' signals that calling it costs nothing, which implicitly encourages use for inspecting efficiency metrics, and the content list implies the use case. However, there is no explicit when-to-use versus siblings such as get_ledger, route_task, or record_route_outcome, and no stated exclusions.

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.