Netfluid

netfluid__fund_card_recharge

Charges a tokenised Visa/Mastercard. Confirm (yes/no) before executing

STEP 2 Charges a tokenised Visa/Mastercard, use /card/quote before this end point The card must have been previously charged using /fund/card_3D_secure_complete @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 wallet_card_id: The wallet_card_id associated with this wallet, can be found with wallet/card_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). @param note: The note on the transaction

@return: a json object

Input Schema

Name	Required	Description	Default
`note`	No
`token`	Yes
`amount`	Yes
`api_key`	Yes
`wallet_fk`	Yes
`account_fk`	Yes
`wallet_card_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026
- changedOutput schema / (root)
```
Previous value: -{
-  "type": "object"
-}New value: +null
```
AddedJul 8, 2026

TDQS

A4.1/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 well: it discloses a real monetary charge, automatic conversion to ZAR, a 3.5% fee plus 15% VAT on the fee portion, and required confirmation. Gaps remain on idempotency/retry behavior and error handling for a financial mutation.

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?

Front-loaded with the action and the confirmation requirement, which is good. However the opening sentence is duplicated ('Charges a tokenised Visa/Mastercard' appears twice), a 'STEP 2' artifact is left in, and '@return: a json object' is pure noise.

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 7-parameter payment mutation with no annotations and no output schema, the definition covers prerequisites, sequencing, fees, and every parameter. What is missing is the shape of the returned JSON (beyond 'a json object') and failure/idempotency semantics.

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 coverage is 0%, so the description must compensate and it does, documenting all seven parameters. It adds non-obvious semantics: account_fk is a database int (not an address) and may not be 0, obtainable from /wallet/accounts_list; wallet_card_id from wallet/card_list; amount is converted to ZAR plus fees.

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 and resource ('Charges a tokenised Visa/Mastercard') and places itself in a sequence ('STEP 2', after /fund/card_quote). It does not name the closest sibling (paywall__wallet_visa_mastercard_recharge) as an alternative, so sibling disambiguation is only partial.

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?

Gives clear preconditions: run /card/quote first, and the card must already have been through /fund/card_3D_secure_complete. It also mandates a yes/no confirmation before executing. No explicit exclusion against the paywall recharge variant, but the context needed to invoke correctly is present.

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

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

Need Help?