Skip to main content
Glama

JestSprout Meme Coin & Solana Rug-Check Tools

Meme coin logo / mascot image generator

memecoin_logo_generator
Read-onlyIdempotent

FREE, no API key (about 100 calls/day). Returns a stable hosted URL for a 512x512 mascot-style coin logo (SVG) made from a ticker, name and theme. Styles: sticker, neon, retro, comic (SVG) or realistic (AI photo matching the name/description, cached). The same inputs always give the same image.

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": {
      "ticker": "<ticker>"
    },
    "name": "memecoin_logo_generator"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoCoin name
styleNoArt style
themeNoTheme words used to pick the mascot (frog, cat, dog, alien, ...)
tickerYesTicker, e.g. FROG
descriptionNoOptional coin description (used by realistic style)

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 only declare readOnly/openWorld/idempotent; the description adds the rate limit, the absence of auth, caching for the realistic style, and the guarantee that identical inputs reproduce the same image. Those are genuinely load-bearing facts an agent could not get from the structured fields.

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?

Three tightly packed sentences, all front-loaded with the free/no-key constraint before the output shape and style taxonomy. No 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?

With no output schema, the description still specifies the return value (stable hosted URL, SVG, 512x512) plus determinism and cost limits. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description earns extra by explaining the role of each input: theme words select the mascot, description only matters for the realistic style. Slight gap: it enumerates only five styles while the enum contains seven (painted and anime are unmentioned).

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 action and artifact: a stable hosted URL for a 512x512 mascot-style coin logo (SVG) built from ticker, name and theme. That is clearly distinct from sibling concept/text tools such as generate_coin_concept or memecoin_name_ticker_ideas.

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?

Provides useful operating context (free, no API key, ~100 calls/day), which tells the agent when the tool is viable. However it never names an alternative or states when NOT to use it versus the sibling concept generators, so routing between them is left to inference.

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