Skip to main content
Glama
Sign In

Netfluid

by io.netfluid.mcp
OverviewDiscussionsAdmin

netfluid__account_merchant_voucher_quote

Performs a quote to before issuing a Netfluid voucher as a merchant.

STEP 1: Performs a quote to issue a voucher as a merchant. Returns the merchant commission as well as the amount charged to the customer. @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 issue the voucher @param amount: The amount to issue the voucher for in up to 2 decimals.

@return: a json object

Input Schema

NameRequiredDescriptionDefault
tokenYes
amountYes
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, the description carries full burden. It partially compensates by disclosing what the call returns (merchant commission and customer-charged amount), which tells the agent this is a non-mutating preview. But '@return: a json object' is uninformative, and prerequisites, quote validity/expiry, and error behavior are unstated.

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 first sentence and the 'STEP 1:' sentence are largely redundant restatements, and the opening line contains a grammatical error ('quote to before issuing'). The parameter block is well organized, but the prose is repetitive rather than front-loaded.

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 4-required-param tool with no annotations and no output schema, the description covers parameters and the substantive return contents (commission, charged amount), but omits authentication flow context beyond parameter notes, quote lifetime, and failure modes. Adequate but with visible gaps.

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 compensate, and it does: it documents all four parameters, including the critical clarification that account_fk is a database integer (not a wallet address) and may not be 0, and that amount is expressed with up to 2 decimals. Format details for token origin (/access/login) are also given.

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 ('Performs a quote to issue a voucher as a merchant') and clarifies it's a pre-step ('STEP 1', 'to before issuing'). It does not name the sibling voucher_issue explicitly, but the sequencing language distinguishes it functionally from the other merchant voucher tools.

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?

The 'STEP 1' framing implies this quote precedes netfluid__account_merchant_voucher_issue, which is useful implied usage. However, there is no explicit when-to-use/when-not statement, no named alternative, and no guidance on what to do with the returned quote.

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