Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

siexchange_quote

Fetches live swap quotes for specified tokens and amounts across supported chains, returning expected output, fee tier, venue, and route before execution.

Instructions

[FREE] Live swap quote from the Super Intelligence Exchange (siexchange.lol). Non-custodial, 5 chains: solana, base, ethereum, polygon, robinhood. Launch-set coins trade FREE: MUSKOX (Solana), ARENA, SOLV, AGWC, GITLAWB (Base

  • Robinhood). Any other token costs $0.02 USDC via x402 per trade (use siexchange_calldata for execution). token_in/token_out accept symbols (ETH, USDC, SOL, MUSKOX, ARENA, SOLV, AGWC, GITLAWB) or contract addresses. amount_in is raw integer units (e.g. 100000000000000 = 0.0001 ETH, 100000000 = 0.1 SOL). Returns amount_out, tier (free|paid), venue, and route. Quotes cost

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": {
      "chain": "<chain>",
      "token_in": "<token_in>",
      "token_out": "<token_out>",
      "amount_in": "<amount_in>"
    },
    "name": "siexchange_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYes
token_inYes
amount_inYes
token_outYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.4/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 well: it discloses non-custodial status, the five supported chains, the exact free token set, the $0.02 USDC x402 charge for other tokens, and the returned fields (amount_out, tier, venue, route). The final sentence is truncated ("Quotes cost "), so the cost of the quote call itself is left ambiguous, and there is no note on failure behavior or 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.

Conciseness4/5

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

The content is dense and front-loaded, with pricing and sibling routing appearing before parameter detail. The one defect is the dangling, cut-off closing clause "Quotes cost " which adds no information and leaves a visible gap.

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?

With no annotations and no output schema, the description supplies the pricing model, chain coverage, accepted token forms, amount encoding, and the shape of the response, which covers everything needed to call it correctly. The truncated sentence and the absence of error/edge-case behavior are the only completeness gaps.

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%, so the description must compensate for all four parameters, and it does: chain is enumerated (solana, base, ethereum, polygon, robinhood), token_in/token_out accept either symbols from a named list or contract addresses, and amount_in is explicitly raw integer units with worked examples (100000000000000 = 0.0001 ETH). This is meaningfully more than the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ("Live swap quote from the Super Intelligence Exchange") and immediately names the sibling that performs the other half of the job ("use siexchange_calldata for execution"). An agent can distinguish quoting from executing without opening either schema.

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 explicitly routes execution to siexchange_calldata and explains the free/paid tiering that determines when a call is free versus $0.02 USDC, which is useful selection context. It stops short of stating when not to use the tool (e.g. unsupported chains or malformed symbols), so it falls just short of fully explicit guidance.

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

Deploy Server

Other Tools