Skip to main content
Glama

pay_invoice

Send payment for an invoice to the vendor's current bank account on record using the invoice ID and amount in cents.

Instructions

Pay an invoice today. The money goes to the bank account currently on the vendor's master record.

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": {
      "invoice_id": "<invoice_id>",
      "amount_cents": "<amount_cents>"
    },
    "name": "pay_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
invoice_idYes
amount_centsYesAmount to pay, in cents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it discloses only that funds route to the bank account on the vendor's master record. It says nothing about whether payment is irreversible, whether approval is required, what happens on insufficient funds or duplicate submission, or what the call returns.

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?

Two short sentences with the action front-loaded and the important fund-routing detail immediately after. Minimal waste, though 'today' is vague enough to be a small liability rather than a gain.

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

Completeness2/5

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

This is a money-moving mutation with no annotations, no output schema, and a half-documented schema, so the description needs to do more than two sentences. Missing irreversibility, approval/permission preconditions, idempotency, and failure behavior leaves an agent under-informed for a high-stakes operation.

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 only 50% — amount_cents is documented, invoice_id is not — so the description should compensate, and it does not. It adds no format, sourcing, or validation guidance for invoice_id and no clarification of the amount (e.g., partial payment, overpayment, or mismatch with the invoice total).

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 resource ('Pay an invoice') and adds the destination of funds, which clearly separates it from read-side siblings like get_invoice or list_invoices. The word 'today' is ambiguous, but the core action is unambiguous.

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 by the verb; there is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as manual_wire, request_approval, or update_vendor_bank when the payee account is wrong. The note about the vendor master record hints at a precondition but never states it as one.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.