Skip to main content
Glama

bank_details

Read-onlyIdempotent

Retrieve the full curated record for a UAE business bank by ID slug to compare banking options and support business setup decisions.

Instructions

Get the full curated record for a UAE business bank.

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": {
      "bank_id": "<bank_id>"
    },
    "name": "bank_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
bank_idYesBank id slug. Examples: "wio", "mashreq_neobiz", "zand", "ruya", "emirates_nbd", "rakbank", "cbd", "adcb", "fab", "adib", "hsbc", "standard_chartered", "citi".

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the notion of a "curated" record (complete vs. summary), and discloses nothing about freshness, caching, or failure behavior for an unknown id.

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?

A single tightly written sentence with no filler and the resource front-loaded. It is not padded, but it is also close to the minimum viable length for a tool of this scope.

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

Completeness3/5

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

With an output schema present and 100% parameter documentation, return values and the single argument need no prose. The remaining gap is routing: nothing tells the agent to call list_banks first to obtain a valid slug, leaving a discovery hole in an otherwise well-structured definition.

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 description coverage is 100% and the bank_id property already carries a rich slug list of examples, so the schema does the heavy lifting. The description adds no format, constraint, or lookup-hint information beyond what the schema provides, which is the expected baseline.

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 ("Get") and a specific resource ("the full curated record for a UAE business bank"), which is clearly distinguishable from list_banks (enumeration) and bank_recommendation (advisory). However, it never names those siblings, so the differentiation is only implicit.

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 "full curated record" implies this is the detail-fetch that follows a listing, but the description gives no explicit when-to-use, no pointer to list_banks for discovering a valid bank_id, and no exclusion relative to bank_recommendation. Usage is only inferable.

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

Deploy Server

Other Tools