Skip to main content
Glama

SovereignRoute + AP2 (Agentic Compute Router & FinOps)

route_trigger_budget_freeze

DestructiveIdempotent

Atomically freeze or unfreeze a tenant RouteBudgetCoordinatorDO spend coordinator and dispatch a <50ms Kavach KYA kill-switch sync.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tenantId": "<tenantId>",
      "frozen": "<frozen>",
      "reason": "<reason>"
    },
    "name": "route_trigger_budget_freeze"
  }
}

Input Schema

NameRequiredDescriptionDefault
frozenYesFreeze state (true to lock spend)
reasonYesAudit reason for circuit-breaker state change
tenantIdYesTarget tenant identifier to freeze

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing atomicity and the guaranteed <50ms propagation to the Kavach KYA kill switch, which an agent could not learn from any structured field. It stops short of describing failure behavior or rollback on a partially applied sync.

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 or repetition, and the atomicity guarantee and latency target are packed efficiently. It is dense with internal acronyms, which slightly harms first-read clarity but does not waste words.

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 destructive, idempotent three-parameter mutation with no output schema, the definition covers what the tool does and its propagation side effect adequately. It is thin on preconditions, required authorization, and what the caller should expect after the call, which matters for a kill-switch operation.

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%, so all three parameters (tenantId, frozen, reason) are already documented in the schema. The description adds no additional meaning about parameter formats, constraints, or interactions, 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 names a specific verb pair (freeze/unfreeze) and a concrete resource (tenant RouteBudgetCoordinatorDO spend coordinator), plus a downstream side effect (kill-switch sync). It is clearly distinguishable from siblings like route_get_savings_ledger or route_classify_prompt, though the heavy internal jargon (DO, Kavach KYA) reduces immediate readability.

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?

The description never states when an agent should freeze vs unfreeze, what preconditions exist, or what alternatives to consider for budget control. Usage must be inferred entirely from the verb and the required 'reason' parameter.

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.