Skip to main content
Glama

Boundra — Payment Approval Gateway for AI Agents

get_policy_versions

Read-onlyIdempotent

View a user's policy version history (version chain + hashes, verifiable against on-chain commitments)

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": {
      "owner": "<owner>"
    },
    "name": "get_policy_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerYesOwner wallet address that scopes policy, budget and audit state

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / owner / description
      Added value: +"Owner wallet address that scopes policy, budget and audit state"
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

The annotations already establish that the operation is read-only, idempotent, and non-destructive. The description adds useful context about the hash-bearing version chain and its verifiability, but leaves history completeness, ordering, and the verification workflow unstated.

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 states the operation and then the distinguishing chain/hash detail. The parenthetical is substantive rather than filler, and there is no repetition or unnecessary wording.

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 one-parameter read-only lookup with an output schema, the description supplies enough information to understand and invoke the tool correctly. It would be more complete with explicit sibling differentiation and any important constraints on history coverage or ordering.

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?

The sole owner parameter is already fully described in the schema as the wallet address scoping policy, budget, and audit state. The description's reference to a user adds no further wallet-format or scoping detail, so the 100% schema-coverage baseline applies.

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?

The description uses a specific verb and resource—viewing a user's policy version history—and identifies the returned version chain and hashes. This implicitly distinguishes it from get_policy for current policy state and get_audit_trail for general audit events.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage contexts: inspecting policy history and obtaining hashes that can be checked against on-chain commitments. It does not explicitly state when to use get_policy or get_audit_trail instead, so the guidance remains implicit rather than providing exclusions or alternative routing.

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.