MemeSwap MCP

memeswap_build

Builds unsigned swap material so the user can buy (or sell) a listed meme coin (POST /api/build); wallet must review and sign. Not a launch/create-token tool. Fee 0.85% on fee-enabled trades. NFA. Does NOT authorize, sign, submit or confirm.

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>",
      "side": "<side>",
      "token": "<token>",
      "amount": "<amount>",
      "from": "<from>",
      "quote": "<quote>"
    },
    "name": "memeswap_build"
  }
}

Input Schema

Name	Required	Description
`from`	Yes	Public signing-wallet address; output is bound to this caller.
`side`	Yes
`chain`	Yes
`quote`	Yes	Prior memeswap_quote /api/quote response object.
`token`	Yes
`amount`	Yes	Positive decimal string
`slippageBps`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 30, 2026

TDQS

A4/5.0

Behavior4/5

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

Adds real value beyond the annotations: the output is unsigned material requiring external signing, trades on fee-enabled swaps carry a 0.85% fee, and the tool stops short of authorize/sign/submit/confirm. The annotations already convey non-read-only, non-idempotent, open-world behavior, so the fee and unsigned-output disclosure are the meaningful increments.

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?

Dense, front-loaded, and the exclusion ('Not a launch/create-token tool') and boundary ('does NOT authorize...') are placed where they matter. Terse fragments are efficient, though 'NFA' is ambiguous jargon for an agent.

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 7-parameter, no-output-schema build tool with 43% schema coverage, the description should say more about what the returned 'unsigned swap material' looks like and confirm the quote-then-build ordering. It covers safety and fees well but leaves parameter and output expectations under-specified.

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 coverage is only 43%, yet the description adds almost no parameter meaning beyond restating side (buy/sell). It never explains chain, amount units, or slippageBps, and only implicitly ties the quote parameter to a prior quote call. Modest help over a thin schema.

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?

States a specific verb and resource ('Builds unsigned swap material') plus scope ('buy (or sell) a listed meme coin') and the backing endpoint. It explicitly rules out the closest confusable sibling job by saying 'Not a launch/create-token tool', so an agent can separate it from create/credential and token tools.

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 clear usage context: this produces material a wallet must review and sign, and it does NOT authorize, sign, submit or confirm. That defines the handoff boundary, though it never explicitly says to call memeswap_quote first (only the schema's quote description implies the ordering) and states no exclusion relative to memeswap_xquote.

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

All MemeSwap MCP tools Inspect

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

Need Help?