Skip to main content
Glama

YESbusiness

Supported EBICS banks

list_supported_ebics_banks
Read-onlyIdempotent

The live catalog of banks YESbusiness can connect through EBICS, including the exact current count. Call it when the user asks whether a named bank is supported, which banks are supported, or how many are supported. An absent bank means only that it is not in the current EBICS catalog; never turn a failed lookup into an unsupported-bank claim.

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": {
      "company_id": "<company_id>"
    },
    "name": "list_supported_ebics_banks"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_idYesThe company to work on — one of list_my_companies' company_id values.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the tool read-only, idempotent, non-destructive, and not open-world. The description adds useful behavioral context that the catalog is live, includes the current count, and must not be interpreted as a definitive unsupported-bank verdict after a failed lookup.

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 front-loaded with what the tool returns, then states when to call it, then gives an important interpretation guardrail. Every sentence contributes useful information and no wording is wasted.

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 simple one-parameter read-only lookup, the description covers purpose, usage, count behavior, and the key caveat about absent banks. It does not specify the exact return shape, but no output schema is provided and the essential calling context is present.

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?

The single company_id parameter is fully documented in the schema, including its UUID format and reference to list_my_companies. The description adds no further parameter-level semantics, so the schema carries the parameter meaning.

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

Purpose5/5

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

The description states a specific resource and operation: a live catalog of EBICS-connectable banks with the exact current count. It clearly distinguishes this lookup tool from the financial-data siblings by focusing on bank support status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit invocation triggers: a named bank support question, a general supported-banks question, or a count question. It also adds a critical usage caveat that an absent bank does not by itself prove unsupported status.

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