Skip to main content
Glama

Juicyway by Nova (CIVAI)

resolve_bank_account

Run the resolve_bank_account pipeline.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "resolve_bank_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
notification_messageNoShort user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. Added
  12. Removed
  13. Added
  14. Removed
  15. Added
  16. Removed
  17. Added
  18. Removed
  19. Added
  20. Removed
  21. First observed

TDQS

D1.9/5.0
Behavior1/5

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

With no annotations, the description carries the full disclosure burden and discharges none of it: it does not say whether this is a read or a mutation, whether it moves money, what external bank API it hits, whether it is idempotent, or what happens on failure. "Pipeline" is a label, not a behavioral disclosure.

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

Conciseness2/5

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

It is one short sentence, but brevity here is under-specification rather than conciseness: the sentence consumes the entire definition without conveying actionable information. Nothing is front-loaded because nothing substantive is present.

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?

No annotations, no output schema, and a single opaque parameter mean the description must explain what the tool does and returns, and it does neither. An agent cannot safely decide to call a bank-account resolution operation on this basis.

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?

Schema coverage is 100% and the single optional notification_message parameter is fully documented in the schema, so the baseline of 3 applies. The description adds nothing beyond it, and notably the only parameter is a fallback message string, which gives no clue about the account data the tool presumably operates on.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Run the resolve_bank_account pipeline" restates the tool name as a pipeline and never says what resolving a bank account actually does (validate an account number? match a beneficiary? clear a pending transfer?). No sibling is differentiated, even though siblings like list_bank_beneficiaries and bank_transfer occupy adjacent territory.

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 indication of when to call this versus bank_transfer, list_bank_beneficiaries, or fetch_kyc_status, nor any stated preconditions. The description offers no guidance at all, leaving routing entirely to guesswork from the name.

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.

Resources