Skip to main content
Glama
Sign In

Netfluid

by io.netfluid.mcp
OverviewDiscussionsAdmin

paywall__wallet_transfer

Transfers amount from wallet_fk, account_fk to the system wallet This tool only transfers the amount, it does not activate or act on the transfer. The sending wallet's PIN is required to perform the transaction. Use it for account top-ups or if successful to log a customer payment. The benefit of using a Netfluid wallet is that Netfluid does not charge a fee on internal transfers, implying a cost saving. Funds received in the system account become credits on the customer account. These credits can then be used to purchase subscriptions. On a successful payment this wallet and account can OPTIONALLY be linked to a customer's subscription. @param from_wallet_fk: The sender Netfluid wallet_fk @param from_wallet_pin: The sender Netfluid wallet PIN @param from_wallet_account_fk: The sender Netfluid account_fk (not account address but the database account_fk), if set to 0, we'll try and find an account_fk that matches the currency_fk=7 (ZAR) and has more than amount available @param amount: The decimal amount to transfer, 2 decimal points @param customer_id: The customer's database id @return: a json object, containing the OTT voucher amounts in the "values" object

Input Schema

NameRequiredDescriptionDefault
amountYes
customer_idNo
from_wallet_fkYes
from_wallet_pinYes
from_wallet_account_fkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "type": "object"
-}New value: +null
  2. Changed4 schema fields changed
    • addedInput schema / properties / from_wallet_account_fk / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / from_wallet_account_fk / default
      Added value: +0
    • removedInput schema / properties / from_wallet_account_fk / type
      Removed value: -"integer"
    • changedInput schema / required
      Previous value: -[
-  "from_wallet_fk",
-  "from_wallet_pin",
-  "from_wallet_account_fk",
-  "amount"
-]New value: +[
+  "from_wallet_fk",
+  "from_wallet_pin",
+  "amount"
+]
  3. Changed1 schema field changed
    • addedInput schema / properties / customer_id
      Added value: +{
+  "default": 0,
+  "type": "integer"
+}
  4. Added

TDQS

A3.7/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 disclose real behavior: the sender's PIN is required, funds land in the system wallet and become customer credits, and the wallet/account can optionally be linked to a subscription on success. It adds the no-fee internal-transfer property, though it omits failure handling, reversibility, and auth/rate limits.

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?

Purpose is reasonably front-loaded and @param/@return tags give structure, but the body rambles with marketing fluff ('implying a cost saving') and an ambiguous, semi-garbled sentence about top-ups/logging payments. Trimming the fluff would sharpen it without losing content.

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?

No annotations and no output schema, so the description must cover both behavior and parameters; it largely does, including the PIN requirement, credit semantics, optional subscription linking, and full parameter coverage. It is let down mainly by an incoherent @return note ('OTT voucher amounts' for a wallet transfer) and no failure/error guidance.

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 description coverage is 0%, so the description must compensate, and it does document all five parameters via @param tags. Most valuable is the from_wallet_account_fk fallback rule (0 => auto-find a ZAR account with sufficient balance), which is absent from the schema; amount's 2-decimal constraint is also given. customer_id is documented only thinly as 'database id', leaving its role in the transfer unclear.

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?

The description states a specific verb and resource ('Transfers amount from wallet_fk, account_fk to the system wallet') and clarifies scope ('only transfers the amount, it does not activate or act on the transfer'). It doesn't explicitly name the sibling it differs from (e.g. paywall__wallet_stablecoin_transfer or paywall__pay_subscription_with_wallet), so differentiation is implied rather than stated.

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?

'Use it for account top-ups or if successful to log a customer payment' gives implied usage context, but the clause is garbled and no alternatives are named or excluded. An agent must still infer when to pick this over wallet_stablecoin_transfer or customer_log_payment.

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