Skip to main content
Glama
Sign In

Netfluid

by io.netfluid.mcp
OverviewDiscussionsAdmin

netfluid__crypto_optout

Opts the blockchain wallet out of holding a digital asset. Confirm (yes/no) before executing

Opts the blockchain wallet out of holding a digital asset. Ensure that the blockchain wallet has a zero balance of this asset, before performing this action as value may be lost. @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 associated with this blockchain wallet @param asset_id: The asset_id or contract address of the digital asset on this blockchain, can be found from /crypto/digitalassets

@return: a json object

Input Schema

NameRequiredDescriptionDefault
tokenYes
api_keyYes
asset_idYes
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.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 meaningful work: it flags the operation as potentially value-destroying and imposes a zero-balance precondition, which an agent must check. It does not describe auth scope or reversibility beyond the api_key/token framing.

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 sentence 'Opts the blockchain wallet out of holding a digital asset' is repeated verbatim immediately after the confirm instruction, and the JSDoc block leaves the return value vague ('a json object'). The substance is present but not tightly front-loaded.

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 4-required-param mutation with no annotations and no output schema, the description supplies the destructive warning, the precondition, and full parameter meaning. Only the return value is left underspecified, which is minor given the tool's nature.

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%, and the description fully compensates: it documents all four parameters, warns account_fk is an int DB ID (not an address, not 0), and tells the agent asset_id is a contract address discoverable from /crypto/digitalassets. This is exactly the compensation a 0%-coverage schema requires.

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 (opts out) and resource (the blockchain wallet re a digital asset), clearly distinguishing it from its inverse sibling netfluid__crypto_optin. However, it never names the sibling or scopes the operation beyond the single wallet/asset pair.

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 two concrete usage conditions: confirm (yes/no) before executing, and ensure the wallet holds a zero balance first or value may be lost. It lacks an explicit pointer to crypto_optin as the inverse operation, but the preconditions are unusually well stated.

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