Skip to main content
Glama

SovereignRoute + AP2 (Agentic Compute Router & FinOps)

route_classify_prompt

Read-onlyIdempotent

Scrub regulated Indian PII in volatile memory, classify prompt complexity in <5ms, and resolve a DPDP/RBI geo-pinned upstream region with projected FinOps savings.

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": {
      "prompt": "<prompt>"
    },
    "name": "route_classify_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
policyNo
promptYesPrompt text to scrub and classify

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare read-only, non-destructive, idempotent, closed-world behavior. The description adds useful context about volatile-memory PII scrubbing, <5ms classification, and geo-pinning with FinOps savings, but it does not explain what data is returned or how policy affects processing.

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 dense sentence with no filler; however, it compresses three operations and jargon, which slightly reduces immediate clarity.

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 two-parameter, no-output-schema tool, the description covers purpose and some behavioral traits but omits policy semantics and the shape of the returned classification/region/savings, so the agent still lacks information needed to invoke confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: prompt is documented, but policy is only an enum with no schema description. The description hints at DPDP/RBI and FinOps relevance but never explains the policy parameter, its default, or how the four policies change scrubbing, classification, or routing.

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 three specific operations—PII scrubbing, prompt complexity classification, and geo-pinned region resolution—with performance and FinOps context. It is distinguishable from ledger/budget/mandate siblings, though it does not explicitly redirect to them.

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, when-not-to-use, or alternative guidance is provided. The policy parameter's role and selection criteria are not addressed, leaving the agent to infer when this tool is appropriate.

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.