Netfluid

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

TableJSON Schema

Name	Required	Description	Default
`token`	Yes
`amount`	Yes
`api_key`	Yes
`wallet_fk`	Yes
`account_fk`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations, the description fully covers the behavioral safety profile: it explicitly states this is a quote-only operation with no charging, details the fee structure (3.5% + 15% VAT), mentions the 10-minute quote validity, and clarifies that conversion to ZAR is automatic. This is critical, non-obvious behavior disclosed clearly.

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 description opens with a clear summary but then repeats the exact same sentence 'Returns a quote for a VISA/Mastercard card charge' verbatim, adding redundancy. The parameter list is structured and helpful, but the duplication could be trimmed without losing meaning.

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 an output schema exists, return-value documentation is not needed. The description covers the operation's purpose, non-charging nature, fees, quote validity, and parameter semantics comprehensively. It does not explicitly cross-reference the actual charge tool in the workflow, which is a minor completeness gap, but the tool's own context is well covered.

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 inline parameter documentation is essential. It adds strong context for account_fk (database ID, not an address, never 0, sourced from /wallet/accounts_list) and amount (currency, ZAR conversion, fee calculation). api_key and token get minimal explanation, and wallet_fk is tautological, but overall the description compensates for the schema gap effectively.

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 it 'Returns a quote for a VISA/Mastercard card charge' and emphasizes it is 'STEP 1' and that 'no cards are charged', effectively distinguishing it from charge-related sibling tools. The verb+resource are specific and unambiguous.

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?

It explicitly says this is 'STEP 1 in charging a tokenised Visa/Mastercard' and that it 'only performs a quote, no cards are charged', making the intended usage clear. However, it does not name the exact charge tool (e.g., netfluid__fund_card_recharge) as an explicit alternative, so a direct when-not-to-use pointer is missing.

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

All Netfluid tools Inspect

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.

TDQS

C2.6/5.0

Disambiguation2/5

Several tools have overlapping or identical purposes (e.g., netfluid__session and netfluid__session_2_token, netfluid__email and netfluid__send_email). With 142 tools spanning wallet, crypto, funding, and paywall features, distinguishing between similar account/crypto/balance tools requires careful reading of descriptions.

Naming Consistency3/5

Most tools follow a snake_case pattern with a netfluid__ or paywall__ prefix, but there are inconsistencies like netfluid__session_2_token, netfluid__netfluid_voucher_check, and single-noun tools (netfluid__skill, netfluid__fees). The two namespaces use slightly different conventions, making the overall set feel less uniform.

Tool Count1/5

At 142 tools, this is an extremely large surface for any MCP server. Even for a comprehensive financial platform, this exceeds practical usability and likely includes duplicates or overly granular operations.

Completeness4/5

The tool set covers a wide range of operations including account management, crypto transactions, funding methods, withdrawals, and paywall subscriptions. However, the presence of duplicate tools suggests redundancy rather than a clean, minimal complete surface, and some workflows may require chaining many tools.

Resources

Need Help?