Skip to main content
Glama

SovereignRoute + AP2 (Agentic Compute Router & FinOps)

route_verify_ap2_mandate

Read-onlyIdempotent

Verify an Ed25519 or ES256 chained AP2 Intent-Cart-Payment mandate bundle against TTL, spending ceiling, and D1 anti-replay nonce uniqueness.

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": {
      "bundle": "<bundle>"
    },
    "name": "route_verify_ap2_mandate"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundleYesAP2 Intent, Cart, and Payment mandate bundle

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 declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the exact validation dimensions — signature algorithms, TTL, spending ceiling, and D1 anti-replay nonce uniqueness — which tells an agent that verification is stateful (anti-replay lookup) and multi-factorial. It stops short of describing outcome semantics or failure modes, keeping it below a 5.

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?

One dense sentence with zero filler; the operation, the input, and all four verification dimensions are front-loaded. Nothing needs trimming and nothing essential is deferred.

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?

For a single-parameter read-only verification tool with full schema coverage and clear annotations, the description covers the operation and checks adequately. The remaining gap is what the tool returns (valid/invalid, failure reasons), which matters more here since no output schema exists to explain it.

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% with a single required parameter already documented as the Intent, Cart, and Payment mandate bundle. The description confirms the bundle is chained and signed with Ed25519 or ES256, which adds modest meaning, but it does not specify the expected internal structure of the nested bundle object. Baseline 3 applies when the schema carries the burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Verify) and a specific resource (chained AP2 Intent-Cart-Payment mandate bundle), plus the exact checks performed: signature algorithms (Ed25519/ES256), TTL, spending ceiling, and D1 anti-replay nonce uniqueness. The sibling tools (classify, ledger, budget freeze) are unrelated operations, so no differentiation is needed.

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 name and description imply this is the validation step for a mandate bundle before trusting it, and the enumerated checks give implicit context for when it applies. However, there is no explicit statement of when to call it versus not, no prerequisite notes (e.g., must the bundle be fetched first?), and no mention of what a caller should do with a failed verification.

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.