Skip to main content
Glama

Boundra — Payment Approval Gateway for AI Agents

get_policy

Read-onlyIdempotent

View the active signed payment policy for an owner (and optionally an agent scope)

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

Input Schema

NameRequiredDescriptionDefault
ownerYesOwner wallet address that scopes policy, budget and audit state
agent_idNoOptional agent identifier for agent-scoped policy or attribution

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / agent_id / description
      Added value: +"Optional agent identifier for agent-scoped policy or attribution"
    • addedInput schema / properties / owner / description
      Added value: +"Owner wallet address that scopes policy, budget and audit state"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-open-world, so safety is covered. The description adds useful scope detail ('active signed' rather than drafts or prior versions), but says nothing about what happens when no policy exists for the owner — an error, an empty result, or a default.

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 scoping qualifiers appear in the first few words.

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?

With an output schema present, return values need no explanation, and annotations carry the safety profile, so this short description is nearly sufficient for a two-parameter read. The one gap is the no-policy-found behavior.

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 both owner and agent_id are already documented in the schema. The description's parenthetical about optional agent scope restates rather than extends that, 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?

States a specific verb ('View') and resource ('signed payment policy') and narrows it with 'active' plus an owner scope, which implicitly separates it from get_policy_versions and revoke_policy. It stops short of naming those siblings, so the differentiation is inferred rather than explicit.

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 word 'active' implies this is for reading the currently effective policy and the parenthetical signals that agent scoping is an optional refinement, but there is no explicit when-to-use or when-to-prefer-an-alternative statement. An agent must infer that get_policy_versions covers history.

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.