Skip to main content
Glama
Sign In

Netfluid

by io.netfluid.mcp
OverviewDiscussionsAdmin

netfluid__withdraw_to_bank

Withdraws to a bank account, anywhere world-wide. Confirm (yes/no) before executing

Withdraws to a bank account, anywhere world-wide. The account currency is the currency in which funds will be paid out. The recipient bank account (rba) must already be set. See /wallet/rba @param api_key: The api key allocated to your application @param token: The wallet_api_token provided by /access/login @param account_fk: The account_fk (this is a database ID (int) not an account address (str) and may not be 0) The account_fk from which to withdraw the funds. @param rba_fk: The rba_fk (recipient bank account id) to pay out to, can be found /wallet/rba_list. @param amount: The amount to withdraw @param note: The note on the transaction

@return: a json object

Input Schema

NameRequiredDescriptionDefault
noteNo
tokenYes
amountYes
rba_fkYes
api_keyYes
account_fkYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "type": "object"
-}New value: +null
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden. It usefully discloses that the recipient bank account must be pre-registered, that the account currency determines payout currency, and that confirmation is expected. It omits reversibility, fees, minimum amounts, and auth/rate-limit behavior for a money-movement operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentence 'Withdraws to a bank account, anywhere world-wide.' is duplicated verbatim near the top, which is wasted space. The param list is front-loaded and readable, but the repetition costs it structure points.

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?

For a 5-required-param financial mutation with no annotations and no output schema, the description covers parameters and one key prerequisite. It leaves the return value as a bare 'a json object' and does not document failure modes or the auth/session flow beyond the token param.

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 0%, so the description must supply all parameter meaning, and it largely does: account_fk is flagged as an int (not address) that may not be 0, rba_fk is tied to a lookup endpoint (/wallet/rba_list), and amount/note are explained. Only minor format details (e.g., amount precision/limits) are missing.

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+resource ('Withdraws to a bank account') and adds scope ('anywhere world-wide'). An agent can distinguish it from siblings like withdraw_to_ott or account_wire by the bank-account target, though no sibling is named explicitly.

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?

Provides prerequisites ('rba must already be set. See /wallet/rba') and a confirmation step ('Confirm (yes/no) before executing'), which imply usage. However, it never states when to prefer this over account_wire or withdraw_to_ott, and the confirmation instruction is vague about mechanism.

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

All Netfluid toolsInspect
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.

Resources