Skip to main content
Glama

internal_transfer_create

Initiate an internal transfer between two bank accounts within your organization, with automatic handling of Strong Customer Authentication (SCA) via polling or fallback.

Instructions

Create an internal transfer between two bank accounts within the same organization. SCA: this operation may require Strong Customer Authentication; the tool polls inline by default (wait=30s) and falls back to a structured pending response so the caller can continue via sca_session_show + sca_session_token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoMaximum seconds (0-120) to poll inline for SCA approval before returning a structured pending response. Use false or 0 for a pure two-step flow (return immediately on SCA required). Default 30.
amountYesAmount to transfer
currencyNoCurrency code (must be EUR)EUR
referenceYesTransfer reference (max 99 characters)
debit_ibanYesIBAN of the account to debit
credit_ibanYesIBAN of the account to credit
sca_session_tokenNoSCA session token from a prior call to bind a previously approved SCA challenge to this retry. When set, no polling occurs and the operation runs exactly once with the token attached.
Behavior4/5

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

With no annotations, the description fully discloses SCA behavior: it may require Strong Customer Authentication, polls inline by default (wait=30s), and falls back to a structured pending response. It also explains the wait parameter and sca_session_token usage, which is explicit and helpful.

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 with zero waste. The first sentence clearly states the purpose, and the second provides essential SCA details. It is well-structured and front-loaded.

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?

The description covers the SCA flow well but lacks details about the return value or response structure. Since there is no output schema, the agent would benefit from knowing what the 'structured pending response' contains. It also does not mention error conditions or idempotency, leaving some gaps for a financial operation.

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?

Schema coverage is 100%, providing baseline clarity. The description adds value by explaining how the wait parameter and sca_session_token interact in the SCA flow, and the default wait value. This goes beyond the schema descriptions.

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 clearly states the tool creates an internal transfer between two accounts within the same organization, using a specific verb and resource. It distinguishes from sibling tools like intl_transfer_create and bulk_transfer_create by specifying 'internal transfer' and 'same organization'.

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 provides clear context on when to use this tool (internal transfers) and details the SCA flow with polling and fallback options. However, it does not explicitly exclude scenarios or name alternative tools, leaving the agent to infer from sibling names.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alexey-pelykh/qontoctl'

If you have feedback or need assistance with the MCP directory API, please join our Discord server