Skip to main content
Glama

manual_wire

Send a one-off wire to any bank account outside the invoice workflow for ad hoc payments.

Instructions

Send a one-off wire to any bank account, outside the invoice workflow.

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": {
      "beneficiary": "<beneficiary>",
      "bank_account": "<bank_account>",
      "amount_cents": "<amount_cents>"
    },
    "name": "manual_wire"
  }
}

Input Schema

NameRequiredDescriptionDefault
referenceNo
beneficiaryYes
amount_centsYes
bank_accountYes

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 at all, the description carries the full burden for a high-stakes, money-moving mutation and mostly does not meet it: it never says the transfer is irreversible, whether approval or a balance check is required, whether the call is idempotent, or what happens on failure. "One-off" hints at non-recurring behavior but that is the only behavioral disclosure offered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler; the core action and scope come first. Nothing is wasted, though the brevity comes at the cost of the missing behavioral and parameter detail noted elsewhere.

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?

For an irreversible financial transfer with three required, undocumented parameters, no annotations, and no output schema, the definition leaves too much unstated: expected parameter formats, preconditions, and post-call behavior are all unknown. An agent could construct the call but could easily misuse amount units or account format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters. The description adds essentially no meaning: it does not explain the currency/units of amount_cents, the expected format of bank_account (routing vs IBAN vs tokenized), who beneficiary refers to, or what reference is for or where it appears. "Any bank account" only marginally signals that unregistered external accounts are accepted.

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 concrete verb and resource ("Send a one-off wire to any bank account") plus a scoping differentiator ("outside the invoice workflow"), which separates it from invoice-payment siblings like pay_invoice. It stops short of naming an alternative tool explicitly, so it is clear but not maximally 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?

The phrase "outside the invoice workflow" implies the situation where this tool applies (ad-hoc payments not tied to an invoice), but there are no explicit when-not conditions, no prerequisites such as funding/approval requirements, and no routing to alternatives such as pay_invoice for invoice-linked payments.

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