Skip to main content
Glama

update_vendor_bank

Changes the bank account on a vendor master record when payment details need updating; requires the vendor ID and new bank account.

Instructions

Change the bank account on a 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": {
      "vendor_id": "<vendor_id>",
      "bank_account": "<bank_account>"
    },
    "name": "update_vendor_bank"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendor_idYes
bank_accountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals only that this mutates persistent master-record data; it says nothing about permissions, verification or callbacks required before an account change, reversibility, audit logging, or what happens to the prior account value. For a bank-detail mutation - a well-known fraud vector - this is a serious shortfall.

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 short sentence, front-loaded with the verb and the target, with zero filler. Its problem is under-specification, not verbosity.

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

Completeness1/5

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

With no annotations, no output schema, and 0% parameter coverage, the description is the only source of behavioral information and it supplies none of what matters. An agent cannot determine format expectations, prerequisites, or side effects for a sensitive write 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 0%, so neither parameter is documented in the schema, and the description does not compensate. It never clarifies the expected form of 'bank_account' (account number, routing/ABA pair, IBAN, or an opaque token) or whether 'vendor_id' is validated against existing vendors, leaving a required financial identifier ambiguous.

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 ('Change') and a precise resource ('the bank account on a vendor's master record'), which is unambiguous about what is being mutated. It does not explicitly distinguish itself from sibling tools, but among the listed siblings none overlap with vendor bank data, so the purpose stands on its own.

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 when-to-use guidance, no preconditions (e.g. vendor must exist, whether approval or dual control is required before an account change), and no mention of alternatives. The agent is left to infer everything about when this call is appropriate.

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