Skip to main content
Glama
Sign In

Netfluid

by io.netfluid.mcp
OverviewDiscussionsAdmin

netfluid__crypto_swap

Swaps a digital asset for another using a Distributed Exchange (DEX) on the blockchain. Confirm (yes/no) before executing

Swaps a digital asset for another using a Distributed Exchange (DEX). The DEX charges fees in performing the swap This tools forces the use of a swap via a blockchain DEX, rather try /account/swap to swap between digital assets @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 digital_asset_fk: The origin digital_asset_fk, get value from /crypto/digitalassets @param to_digital_asset_fk: The destination digital_asset_fk, get value from /crypto/digitalassets @param amount: The amount of the digital asset to swap

@return: a json object

Input Schema

NameRequiredDescriptionDefault
tokenYes
amountYes
api_keyYes
account_fkYes
digital_asset_fkYes
to_digital_asset_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

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that 'The DEX charges fees in performing the swap' and requires a yes/no confirmation before executing, but says nothing about reversibility of a swap, slippage, or permission/auth prerequisites beyond the param tags.

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 purpose ('Swaps a digital asset for another using a Distributed Exchange (DEX)') is front-loaded, but it is restated almost verbatim in the body. The @return line ('a json object') adds nothing, and the mixed first-person prose plus param tags are slightly cluttered.

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?

With no annotations and no output schema, the description covers parameters and the fee/confirmation behavior reasonably well, but the return value is left effectively unexplained and the odd 'Confirm (yes/no)' instruction is not tied to any parameter or flow, leaving a mutation tool somewhat under-specified.

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. It documents all six parameters with meaningful detail, including that account_fk is an integer database ID (not an address) and may not be 0, and that both asset FKs come from /crypto/digitalassets. That is strong value beyond the bare schema.

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+resource ('Swaps a digital asset for another using a Distributed Exchange (DEX)') and explicitly routes away from the /account/swap sibling. However, it never distinguishes itself from the near-identical sibling netfluid__crypto_dex_swap, leaving an obvious ambiguity unresolved.

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 names an explicit alternative ('rather try /account/swap to swap between digital assets') and states the condition that selects this tool (forced blockchain DEX swap), plus 'Confirm (yes/no) before executing'. It gives clear routing context, though it omits when-not-to-use relative to crypto_dex_swap.

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