Skip to main content
Glama

Boundra — Payment Approval Gateway for AI Agents

get_audit_trail

Read-onlyIdempotent

View recent payment-approval audit records for an owner

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of most recent audit records to return
ownerYesOwner wallet address that scopes policy, budget and audit state

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of most recent audit records to return"
    • addedInput schema / properties / owner / description
      Added value: +"Owner wallet address that scopes policy, budget and audit state"
  2. First observed

TDQS

B3.3/5.0
Behavior3/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 fully covered without the description's help. The description adds only that results are 'recent' and limited to payment-approval audit records, without disclosing ordering, truncation behavior, or whether denied/expired approvals are included. With annotations carrying the safety burden, this modest added context is worth a 3.

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 zero filler; the resource and scope arrive immediately. It is not padded, though the brevity leaves room that could have been spent on differentiating guidance rather than being wasted.

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 and rich annotations, the description need not explain return values, and the two parameters are fully documented in the schema. For a simple read-only lookup with default limit 10, this is close to sufficient, with only the meaning of 'recent' and record ordering left implicit.

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 description coverage is 100%: 'owner' is documented as the wallet address scoping policy, budget and audit state, and 'limit' as the max number of most recent records. The description's 'for an owner' and 'recent' merely restate those same ideas and add no format, ordering, or boundary semantics. Baseline applies, with no compensating value.

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 and resource ('View ... audit records') and narrows the domain to 'payment-approval' records scoped 'for an owner', which separates it from siblings like get_spend_report or get_evaluation. It stops short of explicitly contrasting itself with any named sibling, so it is clear but not fully differentiated.

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?

Usage is only implied: an agent can infer this is the tool for inspecting past approval history for a given owner. There is no statement of when NOT to use it, no mention of alternatives such as get_spend_report for aggregated spend or evaluate_payment for a new decision, and no prerequisites.

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.