JestSprout Meme Coin & Solana Rug-Check Tools

bot_whoami: your profile, remaining free calls and quotas

bot_whoami

Read-onlyIdempotent

FREE and NOT counted against your limit. Pass your ONE free key as api_key (or call with no key to see your IP's limits). Returns: whether the key is registered and its Bot Hub profile (handle, name, reputation), free calls used/remaining today (base 100 + bonus) and reset time (00:00 UTC), refuel check-in streak, bonus granted today and whether a check-in is available, generate_coin_concept / generate_full_concept free calls left (5/day), and AI-logo quota left.

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": "bot_whoami"
  }
}

Input Schema

Name	Required	Description	Default
`api_key`	No	Your ONE free JestSprout key (or X-API-Key header). Omit to see IP limits.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Goes beyond the readOnlyHint/idempotentHint annotations by disclosing cost behavior (free, not counted against the limit), quota mechanics (base 100 + bonus, 5/day for concept generators), and the reset boundary at 00:00 UTC. That is real operational context an agent needs for planning. It does not state failure modes for invalid keys.

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?

The most decision-relevant fact ('FREE and NOT counted against your limit') is front-loaded, followed by the key guidance and a scannable return-value list. It is a single dense run-on sentence, but nearly every clause carries information.

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?

There is no output schema, so the description carries the return-value burden, and it does so thoroughly by enumerating the profile fields and each quota counter. Combined with annotations covering the safety profile, an agent has enough to call it correctly; only the overlap with jestsprout_whoami is unaddressed.

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 coverage is 100% and the single api_key parameter is fully documented in the schema, including the omit-for-IP-limits behavior. The description largely restates the schema's own wording, adding no new syntax or format detail, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

It names the resource precisely ('your profile, remaining free calls and quotas') and enumerates the returned items (registration status, Bot Hub profile, free calls used/remaining, reset time, check-in streak, per-tool quotas). An agent knows exactly what it gets back. It does not distinguish itself from the similarly named sibling jestsprout_whoami, which is the main clarity gap.

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 clearly frames when to call: it is FREE and not counted against the limit, so an agent can use it freely to check state before spending calls on generate_coin_concept or memecoin_logo_generator. The 'call with no key to see your IP's limits' path is also spelled out. No exclusion or comparison against jestsprout_whoami is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All JestSprout Meme Coin & Solana Rug-Check Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?