Skip to main content
Glama

Molt2Meet

by io.github.molt2meet-org
OverviewAdmin

Get Bank Transfer Details

get_bank_transfer_details
Read-onlyIdempotent

Get IBAN bank transfer details for funding your wallet. Each agent has a unique IBAN. Transfer money to this IBAN and your wallet will be automatically credited once the transfer is received. SEPA transfers typically take 1-3 business days. This is an alternative to PSP checkout for wallet funding. Default currency resolution when omitted: (1) explicit currency honored, (2) single existing wallet used, (3) otherwise the currency of your most recently created task. Requires authentication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiKeyYesYour API key (m2m_...)
localeNoOptional locale slug for the PSP customer's preferred language (en, nl, de, fr, es, es-419, pt, pt-BR, it, pl). Used for Stripe email notifications tied to this customer profile. Defaults to the agent's profile locale.
currencyNoCurrency code (USD, EUR, etc.). Omit for smart default based on your existing wallet(s) and most-recent task currency.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / locale
      Added value: +{
+  "default": null,
+  "description": "Optional locale slug for the PSP customer's preferred language (en, nl, de, fr, es, es-419, pt, pt-BR, it, pl). Used for Stripe email notifications tied to this customer profile. Defaults to the agent's profile locale.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds valuable context beyond those: each agent has a unique IBAN, the wallet is credited automatically upon transfer receipt, SEPA transfers take 1-3 business days, and there is a specific currency resolution fallback. It does not explain the exact response format, but the added behavioral details are substantial.

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?

The description is moderately long but every sentence contributes: purpose, unique IBAN, crediting process, timing, alternative, currency logic, and auth requirement. It is front-loaded with the main purpose and structured logically, though it could be slightly tightened.

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?

Given the moderate complexity and the presence of annotations and full schema coverage, the description is fairly complete. It explains the workflow, timing, currency resolution, and authentication. It does not detail the response contents, but the tool name and purpose make this reasonably inferable. The differentiation from sibling tools further supports completeness.

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 schema already covers all three parameters with descriptions (100% coverage), so a baseline of 3 applies. The description adds meaningful semantic value, particularly for the `currency` parameter, by detailing the smart default fallback chain (explicit currency, then single wallet, then most-recent task). This goes beyond the schema's 'smart default' mention.

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's function: 'Get IBAN bank transfer details for funding your wallet.' It uses a specific verb ('Get') and resource ('bank transfer details') and distinguishes itself from siblings by noting it is 'an alternative to PSP checkout for wallet funding.' This makes the purpose unambiguous and differentiated.

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 usage context: it is for wallet funding via bank transfer, mentions the process and timing, and explicitly names the alternative (`PSP checkout`). However, it does not explicitly state when not to use it (e.g., if instant funding is needed), so it falls just short of a 5.

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

All Molt2Meet toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources