Skip to main content
Glama
Sign In

Netfluid

by io.netfluid.mcp
OverviewDiscussionsAdmin

netfluid__fund_card_quote

Returns a quote for a VISA/Mastercard card charge.

STEP 1 in charging a tokenised Visa/Mastercard. Returns a quote for a VISA/Mastercard card charge. Cards are charged in ZAR. A fee is levied for each charge. This end point only performs a quote, no cards are charged. The quote is valid for 10 minu @param api_key: The api key allocated to your application @param token: The wallet_api_token provided by /access/login @param wallet_fk: The wallet_fk @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 provided by /wallet/accounts_list @param amount: The amount in currency of the account_fk. All cards are charged in ZAR but a conversion of this amount to ZAR will be automatically performed. On top of this amount a fee with be charged equal to 3.5% for fees and insurance plus South African VAT of 15% (only on the fee portion).

@return: a json object

Input Schema

NameRequiredDescriptionDefault
tokenYes
amountYes
api_keyYes
wallet_fkYes
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

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses that no cards are charged (non-mutating), that cards settle in ZAR, that the quote expires in 10 minutes, and the exact fee model (3.5% plus 15% VAT on the fee portion). It omits auth/permission requirements, but the rich fee, expiry and mutability detail is well beyond structured data.

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 statement 'Returns a quote for a VISA/Mastercard card charge' is repeated verbatim at the start and after the STEP 1 line, and the text is truncated mid-word ('10 minu'). The STEP 1 workflow cue is usefully front-loaded, but the duplication and truncation cost it.

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 five-required-param, no-output-schema tool, the description covers purpose, sequencing, fee behavior, quote validity and every parameter. The weak point is the return value, which is only '@return: a json object' — an agent gets no sense of the quote fields, though that is the sole gap.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate, and it documents all five parameters. Notably it warns account_fk 'may not be 0', clarifies it is a database int not an address, points to /wallet/accounts_list as the source, and explains amount is converted to ZAR with a fee applied — meaning far beyond the bare schema types.

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?

States a specific verb and resource ('Returns a quote for a VISA/Mastercard card charge') and frames it as 'STEP 1 in charging a tokenised Visa/Mastercard', which distinguishes the quote from the actual charge. An agent can tell this apart from netfluid__fund_card_recharge without opening either schema.

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?

'STEP 1 in charging a tokenised Visa/Mastercard' gives clear sequencing context, and 'This end point only performs a quote, no cards are charged' clarifies when this is the right call versus the charging step. It does not explicitly name the follow-up sibling tool, so it stops short of a full when/when-not/alternatives statement.

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