Skip to main content
Glama

JestSprout Meme Coin & Solana Rug-Check Tools

Meme coin vibe check / memeability score

memecoin_vibe_check_score
Read-onlyIdempotent

FREE, no API key (about 100 calls/day). Scores how memeable a coin name and ticker are (0-100), with reasons and tips. A fun heuristic, not a price prediction.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCoin name
themeNoOptional theme
tickerYesTicker

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and open-world behavior. The description adds valuable operational details beyond that: free access, no API key requirement, a rough daily quota, output content (score with reasons and tips), and the heuristic limitation.

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 short and front-loaded: access/cost context first, then the core scoring behavior, then the limitation. Every clause contributes information an agent or caller needs.

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 simple two-required-parameter scoring tool with no output schema, the description explains the output range and that reasons and tips are included. The main remaining gap is that it does not explain the optional theme parameter or give explicit sibling routing guidance, but the core invocation context is complete.

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 three parameters are already documented in the schema. The description mentions the scored inputs (name and ticker) but does not meaningfully explain the optional theme parameter beyond the schema, 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?

The description states a specific verb and resource: it scores how memeable a coin name and ticker are on a 0-100 scale. This clearly distinguishes it from sibling tools that generate name ideas, check ticker availability, or assess rug risk.

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?

It gives useful usage context: free, no API key, about 100 calls/day, and explicitly says it is a fun heuristic rather than a price prediction. It does not explicitly compare against sibling tools, but the intended context and one exclusion are clear.

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