Skip to main content
Glama

JestSprout Meme Coin & Solana Rug-Check Tools

JestSprout Pay handle lookup

jestsprout_pay_lookup
Read-onlyIdempotent

FREE, no API key (about 100 calls/day). Look up the public pay addresses for a JestSprout Pay @handle: Solana address, optional Base/EVM address, Solana Pay link, page age and report count. Non-custodial — pay the returned address directly (works for bot-to-bot / x402 payments).

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": {
      "handle": "<handle>"
    },
    "name": "jestsprout_pay_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesPay handle, with or without @, e.g. jestsprout

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly, openWorld, and idempotent behavior. The description adds valuable context beyond annotations: free access, rate limit, non-custodial nature, and what information is returned.

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?

Front-loads the key constraints (free, no API key, rate limit), then states the action and return fields in one compact sentence. No wasted wording.

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?

For a simple read-only lookup with no output schema, the description adequately explains what will be returned and the non-custodial, direct-payment behavior. Combined with annotations and full parameter documentation, 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.

Parameters3/5

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

Schema description coverage is 100%, and the single handle parameter is already documented with format guidance (with or without @). The description adds no additional parameter semantics beyond the schema, so a 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?

Specific verb and resource: "Look up the public pay addresses for a JestSprout Pay @handle" and it enumerates what is returned (Solana address, optional Base/EVM address, Solana Pay link, page age, report count). No sibling tool provides this lookup, so the purpose is unmistakable.

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?

Provides clear usage context: free, no API key, about 100 calls/day, non-custodial, and suitable for bot-to-bot/x402 payments. It does not explicitly say when not to use it or name alternatives, but none of the sibling tools overlap meaningfully.

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