fibx

Official

by Fibrous-Finance

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Send Tokens

send_tokens

Destructive

Transfer native or ERC-20 tokens to a recipient address on Base, HyperEVM, or Monad; set simulate=true for a no-broadcast preview and gas estimate when available.

Instructions

Send native tokens (ETH, cBTC, HYPE, MON) or ERC-20 tokens to a recipient address. If token is omitted, the chain's native token is used. Set simulate=true for a no-broadcast preview; a gas estimate is returned where available.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "amount": "<amount>",
      "recipient": "<recipient>"
    },
    "name": "send_tokens"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	No	Target blockchain network	base
`token`	No	Token symbol (e.g. 'USDC', 'ETH'). Omit for native token transfer.
`amount`	Yes	Amount to send (e.g. '0.1', '100')
`simulate`	No	Set true for a no-broadcast preview; gas estimates may be unavailable
`recipient`	Yes	Recipient address (0x...)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.10.2Nov 8, 2026

changedInput schema / properties / chain / enum

Previous value: -[
-  "base",
-  "citrea",
-  "hyperevm",
-  "monad"
-]New value: +[
+  "base",
+  "hyperevm",
+  "monad"
+]

First observedv0.1.0Jul 30, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, readOnlyHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavior beyond that: that a no-broadcast preview is possible and that a gas estimate is returned where available. It omits that funds movement is irreversible and that prior wallet connection/auth is likely required, keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the primary action and followed by conditional behavior. Every sentence carries information, though the native-token default is duplicated between description and schema, which is mild redundancy.

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 destructive, value-moving tool with no output schema, the definition leaves out key context an agent needs: that a wallet must be connected/authorized first, and that a transaction hash or status would be retrievable via get_tx_status. The simulate and gas-estimate notes help but do not fully close the gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description only restates what the schema already says (token omitted means native token; simulate means no broadcast), adding no format, precision, or chain-specific detail beyond the structured fields.

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 (send native or ERC-20 tokens to a recipient address) and even enumerates supported native symbols (ETH, cBTC, HYPE, MON). It is clearly distinguishable from swap_tokens in the sibling list, though no sibling is named explicitly to reinforce the boundary.

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?

Provides one useful usage cue (set simulate=true for a no-broadcast preview) and a defaulting rule when token is omitted. However there is no guidance on prerequisites such as needing a connected/authenticated wallet, and no exclusion pointing to swap_tokens when the intent is conversion rather than transfer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.