Skip to main content
Glama

SovereignRoute + AP2 (Agentic Compute Router & FinOps)

route_get_savings_ledger

Read-onlyIdempotent

Inspect live RouteBudgetCoordinatorDO daily/monthly USD spend, freeze state, and idempotency key count for the authenticated tenant.

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

Input Schema

NameRequiredDescriptionDefault
tenantIdNoOptional tenant identifier override

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the description only needs to add context — and it does: it discloses that data is "live" rather than cached and enumerates exactly which state fields are returned. It stops short of noting any auth/permission nuance beyond the tenant scoping already implied.

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?

A single front-loaded sentence with no filler; the resource and the three returned data points are packed in without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter read tool with rich annotations and no output schema, the description covers exactly what is missing: the concrete return contents (spend figures, freeze state, key count) and the tenant scoping behavior. Nothing an agent needs to call it correctly is absent.

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?

Schema coverage is 100%, so the baseline is 3; the description adds genuine meaning by stating that results are scoped to the "authenticated tenant," which clarifies what happens when the optional tenantId override is omitted. That is added value beyond the schema's "Optional tenant identifier override".

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?

Uses a specific verb ("Inspect") with a named resource (RouteBudgetCoordinatorDO) and enumerates the returned facts: daily/monthly USD spend, freeze state, and idempotency key count. It implicitly contrasts with route_trigger_budget_freeze by being read-only inspection, though it never names that sibling.

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?

The phrasing "Inspect live ... spend, freeze state" implies the use case (checking budget status before or after routing decisions), but there is no explicit when-to-use, when-not-to-use, or pointer to route_trigger_budget_freeze as the mutating alternative. Guidance is inferred rather than stated.

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.