Skip to main content
Glama

Approve a paid check

approve_check
DestructiveIdempotent

Spends prepaid funds. Runs the quoted check within its ceiling and the person’s daily allowance; new matches go to the alert’s channels. Call only after the person approves this spend. Failed attempts are charged at cost plus margin. Starts no ongoing monitoring.

Permission: work:execute. Ask the person before calling.

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": {
      "check_id": "<check_id>",
      "request_hash": "<request_hash>"
    },
    "name": "approve_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
check_idYesThe check ID returned when it was quoted or created.
request_hashYesThe exact request_hash from the quote. Approval fails if anything changed since the quote.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag a destructive, open-world, idempotent write, but the description adds real behavior the annotations cannot express: charges hit prepaid balance, spending is bounded by a quote ceiling and a daily allowance, failed attempts still cost 'cost plus margin,' and new matches route to the alert's channels. It also supplies the required permission scope (work:execute) and a human-approval gate, which is exactly the kind of context an agent needs before a money-spending call.

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?

The text is dense and front-loaded with the money-spending fact, then constraints, then the permission line. The only waste is mild redundancy between 'Call only after the person approves this spend' and the closing 'Ask the person before calling,' which restates the same human-approval requirement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, billable, two-parameter mutation with an output schema already covering returns, this covers everything that matters: cost model, budget ceilings, approval prerequisite, permission scope, side effects on alert channels, and the absence of ongoing monitoring. Nothing needed to call it correctly is missing.

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?

Both parameters are fully documented in the schema (100% coverage), including that request_hash must be unchanged since the quote. The description adds only the general frame that the check 'within its ceiling' is honored, without elaborating on either parameter beyond what the schema already states, so the baseline 3 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 concrete verbs and a concrete resource: it 'spends prepaid funds' and 'runs the quoted check.' It also states a boundary ('starts no ongoing monitoring') that separates this spend action from the alert-monitoring siblings, so an agent can tell what this tool does and does not do without opening a schema.

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 a clear precondition ('Call only after the person approves this spend' / 'Ask the person before calling') and implies that this only makes sense after a quote exists. However, it never names which sibling produces the quote or when to prefer cancel_check or get_check instead, so the guidance is strong but not exhaustive.

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