Skip to main content
Glama

Approve payment

purch_approve_bill
Destructive

A person approves paying a bill, optionally by a date. Approval is not payment: the money moves in their bank. HUMAN-ONLY: this act is refused to you whatever your role — Approving a payment is a person's decision about their own money. Ask your human to do it. Refused to you whatever your role. Show the person the bill and what is due around it (purch_payables), and let them approve it in the app. Effects: bill approved for payment.

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": {
      "bill_id": "<bill_id>"
    },
    "name": "purch_approve_bill"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoAnything about it ("pay after the client's payment lands").
pay_byNoWhen to pay it by. Defaults to its due date. ISO date, YYYY-MM-DD.
bill_idYesThe bill, e.g. B-0001.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare it as destructive and non-idempotent; the description adds the crucial semantic that approval is not the same as moving money, that funds settle in the person's bank, and that the effect is the bill being approved for payment. It also discloses the access-control behavior (human-only, refused regardless of role), which annotations cannot express. That is substantive disclosure well beyond the structured fields.

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 definition is front-loaded and short, leading with what the tool does and then the human-only constraint and the effect. It loses a point for redundancy: 'Refused to you whatever your role' appears twice in near-identical phrasing, which is wasted space in an otherwise tight block.

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 human-only, single-required-parameter mutation with no output schema, the description covers everything an agent needs: what it does, why the agent must not call it, what to do instead, and the resulting effect. Nothing material is left for the agent to guess.

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?

With 100% schema description coverage, the schema already documents bill_id, pay_by, and note, including the ISO format and the due-date default. The description only echoes 'optionally by a date' without adding syntax, constraints, or interaction rules between parameters. Baseline 3 is appropriate since the schema carries the parameter burden.

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 names a specific verb and resource ('A person approves paying a bill, optionally by a date') and immediately distinguishes it from the adjacent concept ('Approval is not payment: the money moves in their bank'). It also names the sibling tool to use for context (purch_payables), so an agent can distinguish this from purch_record_bill_payment and purch_reject_bill without inspecting schemas.

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

Usage Guidelines5/5

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

Usage is unambiguous: the tool is refused to the agent whatever its role, and the prescribed alternative is to ask the human. It goes further and specifies the concrete fallback flow — show the person the bill and what is due around it via purch_payables and let them approve it in the app. There is no inference required about when this tool is or is not the right call.

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.