Skip to main content
Glama

JestSprout Meme Coin & Solana Rug-Check Tools

Build an UNSIGNED Solana swap transaction (you sign)

solana_swap_unsigned_tx
Read-onlyIdempotent

FREE, no API key (about 100 calls/day). Builds an unsigned Jupiter swap transaction (base64 versioned tx) for YOUR wallet public key. JestSprout never sees keys or funds. A 0.50% (50 bps) integrator fee is added only when the site fee account is active. You sign and send it yourself. Includes a rug check. Not financial advice.

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": {
      "side": "<side>",
      "mint": "<mint>",
      "amount": "<amount>",
      "user_public_key": "<user_public_key>"
    },
    "name": "solana_swap_unsigned_tx"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesToken mint address
sideYesbuy = SOL -> token, sell = token -> SOL
amountYesAmount of input asset
slippage_bpsNoSlippage in bps (default 100)
user_public_keyYesYour wallet public key (base58). Never send a private key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint, openWorldHint, and idempotentHint, but the description adds material behavior: no API key, roughly 100 calls/day, an integrator fee of 50 bps applied only when the site fee account is active, and an assurance that keys and funds are never seen. These are exactly the operating constraints an agent needs before choosing this tool, and they go well beyond what the structured fields provide.

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

Conciseness5/5

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

The description is a tight sequence of short sentences that front-loads the cost and rate limit before describing the output artifact. Marketing-flavored fragments like 'FREE' and 'Not financial advice' are small but still convey access terms, and no sentence restates the schema or the title verbatim.

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 transaction-building tool with no output schema, the description covers the important gaps: the return is a base64 versioned transaction, the caller must sign and send, and a fee may apply. It does not describe failure modes or what the rug-check result looks like, which is a modest remaining gap given five parameters and no output contract.

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 all five parameters (side, mint, amount, slippage_bps, user_public_key) are already documented with formats and bounds. The description adds no per-parameter detail such as whether amount is decimal or raw units, so it neither compensates for nor extends the 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 names a specific verb and artifact: 'Builds an unsigned Jupiter swap transaction (base64 versioned tx) for YOUR wallet public key.' That is far more precise than the tool name alone and makes clear it returns an unsigned payload rather than executing a trade. It does not explicitly contrast itself with solana_swap_quote, so sibling differentiation is implied rather than stated.

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?

Usage is implied through 'You sign and send it yourself,' which tells the agent this is the pre-signing step of a swap flow, and 'Includes a rug check' hints at a safety pass. There is no explicit instruction to call solana_swap_quote first, no stated when-not condition, and no guidance on what to do if the rug check fails.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources