Skip to main content
Glama

MoneyTools payment-safety suite

Approval status

approval_status
Read-only

Check whether the human approved, denied or let the request expire (free). Approved results include receipt_jws (also aliased as proof).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "approval_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
waitNoOptional long-poll seconds for get/status (Relay max 25 without SSE)
agentTokenNoLegacy; ignored for Relay requests (apr-… ids)
approval_idNo
wait_secondsNoOptional long-poll seconds for get/status (Relay max 25 without SSE)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the rest, and it does: it enumerates the three terminal states (approved/denied/expired) and discloses that approved results carry receipt_jws aliased as proof. It stops short of saying anything about polling with wait or whether an expired status is terminal.

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 the result states up front and the payload detail second. The dangling '(free)' is slightly awkward but costs almost nothing.

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?

It covers the key return field even though no output schema exists, which is genuinely useful. For a zero-required, five-parameter status tool with duplicate id and wait parameters, however, it leaves the agent guessing which parameter pair to use and how long-polling affects the response.

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 60% and the description adds no parameter meaning at all. It is silent on the two obvious ambiguities: id versus approval_id and wait versus wait_seconds, plus what the legacy agentToken does when an apr- id is supplied.

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 and the exact outcome set it reports: approved, denied, or expired, plus the receipt_jws/proof payload. That is far more than restating the title, though it never names or contrasts with siblings like approval_verify or approval_consume.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative. The parenthetical '(free)' hints that cost should steer the choice away from a paid sibling, but the agent is left to infer that from a single word rather than a stated rule.

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.

Resources