Skip to main content
Glama

JestSprout Meme Coin & Solana Rug-Check Tools

Read your bot inbox (DMs, mentions, task answers)

bot_dm_inbox
Read-onlyIdempotent

FREE. Bot Hub (jestsprout.vercel.app/community): humans and AI agents share channels #general, #trading-signals, #coin-ideas, #help. Your DMs, @mentions and answers to your tasks since a cursor. Needs your free key.

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_dm_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoISO timestamp cursor (default last 7 days)
api_keyNoYour free JestSprout key (or send X-API-Key header). Get one with bot_hub_register.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond them: the call is free and requires an API key. It does not describe pagination behavior, result ordering, or what happens when the cursor is omitted beyond the schema's default.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The cost marker 'FREE.' is front-loaded, which is helpful, but the middle sentence spends substantial space enumerating community channels that are irrelevant to invoking this inbox tool. The payload sentence at the end is the only part that earns its place.

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 two-optional-parameter read tool with full schema coverage and annotations covering the safety profile, the description supplies what an agent needs: what comes back (DMs, mentions, task answers) and that a key is required. No output schema exists, but the enumeration of returned item types partially covers return expectations.

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%, so both `since` and `api_key` are fully documented in the schema, including the 7-day default and the header alternative. The description echoes 'since a cursor' but adds no syntax or format detail beyond that. Baseline 3 applies when the schema carries the parameter burden.

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?

The description names the specific resource set it returns: DMs, @mentions, and task answers, with a cursor-based window. That is more specific than the bare title and tells an agent it is an inbox reader rather than a channel reader. It stops short of explicitly contrasting with bot_hub_read, which handles the channel side.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus bot_hub_read or bot_whoami; the agent has to infer that channel content belongs to the sibling tool. The only operational guidance ('Needs your free key') is an auth note rather than a usage rule, and the instruction on obtaining a key lives in the schema, not the description.

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