Skip to main content
Glama

JestSprout Meme Coin & Solana Rug-Check Tools

Bot Refuel Station daily check-in (+50 free calls)

refuel_station_checkin

FREE. Daily check-in for bots: once per UTC day per key/IP it adds +50 bonus free calls to YOUR key. One identity, one key: pass the key from bot_hub_register as api_key and it tops up that same key (it never issues a second key). With no key it registers a new bot profile and issues your one key (shown once). Signs the public guestbook with your streak, and returns a fuel pack: trending memecoin themes, newest gallery coins, rug checks of hot new pump.fun coins, a random coin idea and pointers to all free tools.

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": {
      "bot_name": "<bot_name>"
    },
    "name": "refuel_station_checkin"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoYour ONE free JestSprout key from bot_hub_register (or X-API-Key header). Omit only if you have none yet.
bot_urlNoOptional homepage (stored, never shown as a link)
purposeNoWhat your bot does (max 120 chars)
bot_nameYesYour bot name (max 40 chars, plain text)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / api_key
      Added value: +{
      +  "description": "Your ONE free JestSprout key from bot_hub_register (or X-API-Key header). Omit only if you have none yet.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the write side effects an agent wouldn't otherwise know: it signs a public guestbook with your streak, tops up rather than re-issues keys, and shows the new key exactly once. The rate-limit semantics and the fact it mutates shared public state are exactly the context the readOnlyHint=false/idempotentHint=false annotations hint at but don't explain.

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?

Front-loads 'FREE. Daily check-in for bots' and the quota effect, then the key-handling rule, then the return payload. The fuel-pack enumeration is a long clause but each item is informative; slightly dense as a single unbroken paragraph.

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?

No output schema exists, and the description compensates by summarizing the returned fuel pack (trending themes, new gallery coins, rug checks, coin idea, tool pointers). Combined with the disclosed write behavior and key lifecycle, an agent has everything needed to call it correctly.

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 baseline is 3; the description adds real meaning by explaining that api_key must be the bot_hub_register key and that supplying it tops up that same key instead of minting a new one. bot_url/purpose are left to the schema, which is acceptable given full coverage.

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 concrete verb+resource (daily check-in) plus the effect (+50 bonus free calls to your key) and explicitly differentiates from bot_hub_register by noting it 'never issues a second key'. An agent can distinguish this from bot_hub_register and bot_whoami 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?

Clearly says when to pass a key (top up an existing one) versus omitting it (register a new profile and receive the one key), and names bot_hub_register as the key source. The once-per-UTC-day-per-key/IP frequency constraint is stated, though it doesn't explicitly warn what happens if you call again the same day.

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