SwapWallet | سواپ‌ولت

Verified IBANs

get_ibans

Read-onlyIdempotent

The user's verified bank accounts, usable as a Rial withdrawal destination.

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": "get_ibans"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`items`	Yes	The user's verified bank accounts.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "items": {
+      "description": "The user's verified bank accounts.",
+      "items": {
+        "properties": {
+          "bank": {
+            "description": "Bank the IBAN belongs to."
+          },
+          "id": {
+            "description": "Bank account id."
+          },
+          "number": {
+            "description": "IBAN, usable as request_fiat_withdraw's iban."
+          },
+          "ownership": {
+            "description": "Whether the IBAN is the user's own account."
+          },
+          "status": {
+            "description": "Verification status."
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}

First observedOct 12, 2026

TDQS

A3.7/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 closed-world, so the safety profile is covered. The description adds genuine context beyond that: only *verified* accounts are returned (an implicit filter) and their purpose is withdrawal destinations. It does not state error/empty behavior, but with an output schema present the return shape needn't be described.

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 compact sentence with no filler, front-loading the resource and appending the one useful qualifier (Rial withdrawal destination). Every clause earns its place.

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 zero-parameter, read-only getter with rich annotations and an output schema, the description covers what is returned and its purpose. The only gap is the absence of guidance on when this list should be fetched instead of related balance/transaction tools.

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

Parameters4/5

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

The tool takes zero parameters, so per the baseline this scores 4; there is nothing for the description to disambiguate.

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 names the specific resource returned (the user's verified bank accounts) and even its domain role (a Rial withdrawal destination), which is enough to distinguish it from get_balance, get_transactions, and get_deposit_address. It is a noun phrase rather than a verb+resource statement, and it never explicitly contrasts itself with the closest sibling (get_deposit_address), so it falls short of 5.

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?

Usage is only implied by the phrase 'usable as a Rial withdrawal destination' — an agent can infer this tool feeds withdrawal flows, but there is no explicit when-to-use, when-not, or named alternative. No exclusions or prerequisites are given.

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

All SwapWallet | سواپ‌ولت tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.