Skip to main content
Glama

update_my_bank

Update the coach's own payout bank account (confirm-gated). This is where Trainzilla sends the coach's earnings — get explicit confirmation of the exact account/IFSC from the coach before calling with confirm: true, this tool's own preview is not enough given how consequential a wrong account number is.

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": {
      "accountHolderName": "<accountHolderName>",
      "accountNumber": "<accountNumber>",
      "ifscCode": "<ifscCode>",
      "bankName": "<bankName>"
    },
    "name": "update_my_bank"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
bankNameYes
ifscCodeYes
accountNumberYes
accountHolderNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the operation is confirm-gated, that a false/omitted confirm returns only a preview, and that a wrong account number is consequential. This is valuable behavioral context for a mutation tool. It does not explain whether existing bank details are replaced or how in-flight payouts are affected, so it is not exhaustive.

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?

The description is two sentences, front-loaded with purpose and followed by the critical confirmation warning. Every clause earns its place by clarifying scope, behavior, or risk.

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

Completeness4/5

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

For a consequential financial mutation with no output schema, the description covers the essential confirmation protocol and explains where the account is used. It is missing sibling routing and fuller parameter semantics, but the core risk and gating behavior are adequately disclosed.

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 description coverage is only 20%, so the description should compensate for the four undocumented fields. It mentions account/IFSC exactness and confirm: true, but it does not explain accountHolderName, bankName, or the expected IFSC format. Most parameter meaning is left to bare schema types and minLength constraints.

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?

The description uses a specific verb and resource: 'Update the coach's own payout bank account.' It adds useful scope by saying this is where Trainzilla sends the coach's earnings, so the agent knows the account's significance. It does not explicitly distinguish this from related siblings such as update_my_direct_payment or update_my_global_payout, so it falls short of a 5.

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?

The description gives a clear procedural precondition: get explicit confirmation of the exact account/IFSC from the coach before calling with confirm: true. It also warns that the tool's own preview is not sufficient. It does not say when to use this versus sibling payment or payout tools, which keeps it from a 5.

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.