Skip to main content
Glama

JestSprout Meme Coin & Solana Rug-Check Tools

Meme coin ticker / name availability check

memecoin_ticker_availability_check
Read-onlyIdempotent

FREE, no API key (about 100 calls/day). Checks whether a meme coin ticker symbol or name is already used on Solana (DexScreener-indexed tokens, pump.fun included) or in the JestSprout gallery, before you launch. Lists matching mints with liquidity and creation date.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "memecoin_ticker_availability_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional coin name, e.g. Moon Frog
tickerNoTicker symbol, with or without $, e.g. FROG

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover readOnly, openWorld, and idempotent behavior. The description adds substantial context beyond them: no API key requirement, approximate daily rate limit, data sources checked, and expected return content (matching mints with liquidity and creation date).

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?

Front-loads the free/no-API-key constraint, then states the purpose and scope, then describes the result in three compact sentences. Every sentence adds useful information with no repetition or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only lookup with full schema coverage and no output schema, the description is complete enough: it covers cost/rate limit, data sources, intended timing, and the shape of returned matches.

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%, and the schema already defines both optional parameters with examples. The description mentions ticker/name checking but adds no additional format, normalization, or selection guidance beyond what the schema provides, so baseline 3 is appropriate.

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 check action ('checks whether a meme coin ticker symbol or name is already used') and names the exact scope: Solana DexScreener-indexed tokens, pump.fun, and the JestSprout gallery. Its availability-check framing distinguishes it from idea-generation and rug-check siblings.

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 a clear usage context ('before you launch') and useful cost constraints ('FREE, no API key, about 100 calls/day'). It does not explicitly name or compare alternatives such as memecoin_name_ticker_ideas or solana_token_rug_check, so it is clear but not fully alternative-aware.

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