Skip to main content
Glama

JestSprout Meme Coin & Solana Rug-Check Tools

Solana swap quote (Jupiter, non-custodial) + rug check

solana_swap_quote
Read-onlyIdempotent

FREE, no API key (about 100 calls/day). Quote for swapping SOL to/from any Solana token via Jupiter, with a rug-check risk score for the token. A 0.50% (50 bps) JestSprout fee is added only when the site fee account is active. No custody, no trade executed. 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>"
    },
    "name": "solana_swap_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesToken mint address
sideYesbuy = SOL -> token, sell = token -> SOL
amountYesAmount of the input asset (SOL for buy, tokens for sell), e.g. 0.1
slippage_bpsNoSlippage in bps (default 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered; the description goes further by disclosing a rate limit (~100 calls/day), no API key requirement, a conditional 0.50% fee tied to an active site fee account, and that no custody or execution occurs. It omits whether quotes expire and how fees are surfaced in the result, so it is strong but not exhaustive.

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?

Four short sentences, front-loaded with the cost and rate-limit constraint that matters most before invoking. The 'Not financial advice' closer is boilerplate rather than decision-relevant, but overall there is little waste.

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?

There is no output schema, so the description carries the burden of explaining what a quote returns, yet it only mentions a rug-check risk score and stays silent on route, price impact, fee breakdown, and expiry. For a quote tool whose value is entirely in the returned data, that leaves a meaningful gap, though the fee and rate-limit disclosures keep it above the minimum.

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%, with each of the four parameters documented, including enum values for 'side' and a default for 'slippage_bps'. The description reinforces the buy/sell directionality ('SOL to/from any Solana token') but adds no syntax, bounds, or format details beyond what the schema already states, so baseline 3 applies.

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?

Names a specific verb and resource ('Quote for swapping SOL to/from any Solana token via Jupiter') plus the additional rug-check risk score, and the phrase 'No custody, no trade executed' separates it from the sibling that produces an unsigned transaction. An agent can identify which tool builds a quote versus executes a swap without opening any 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?

Usage context is clear: this is the preview/quote step, non-custodial, with no trade executed, which implicitly directs the agent to it before any swap execution. It stops short of naming the alternative tools (e.g., the unsigned-tx sibling or the standalone rug-check tool) or stating when-not to use it, so no explicit routing rule is given.

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