Skip to main content
Glama

loophole-tape

by io.github.gosadu
OverviewDiscussionsAdmin

Creator (dev wallet) reputation ($0.02)

creator_reputation
Read-onlyIdempotent

$0.02 USDC per call. Use to judge a new memecoin by its creator's earlier pump.fun launches on Solana (graduated or rugged) before buying; for the launch's own live evidence use the compact check (GET /v1/check/mint) or the full card (GET /v1/mint/{mint}). Input: address (base58 wallet). Creator stats over every launch we have seen from this wallet, counting only outcomes known at request time: n_launches, resolved, graduations witnessed at >= 84 SOL, rugs by drain or dev dump, median seconds to the dev's first sell, total dev buys; the last 25 launches with outcomes; the creator's live mints right now; and whether the wallet was funded in the last 30 min (warm launch). Empty stats (is_first_time=true) for a wallet we never saw launch. Returns JSON envelope with data{creator, stats{n_launches, n_resolved, grad_rate, rug_rate, median_dev_sell_s, is_first_time}, recent_launches[], live_mints[], funded_recently_by}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesbase58 Solana wallet address (32-44 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / address / examples
      Previous value: -[
-  "9HkwyUhDMyjbpSpnyu5xuZ9vRaFQeajnJsavhie7XcsT"
-]New value: +[
+  "11111111111111111111111111111111"
+]
  2. Changed4 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"base58 Solana wallet address (32-44 chars)"
    • addedInput schema / properties / address / examples
      Added value: +[
+  "9HkwyUhDMyjbpSpnyu5xuZ9vRaFQeajnJsavhie7XcsT"
+]
    • addedInput schema / properties / address / maxLength
      Added value: +44
    • addedInput schema / properties / address / minLength
      Added value: +32
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the per-call cost, data freshness semantics ('outcomes known at request time'), edge-case behavior ('is_first_time=true' for unseen wallets), and definitions like warm-launch funding and rug criteria. This gives the agent a reliable behavioral model of the call.

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 description is dense and front-loaded with the most actionable information: price, purpose, alternatives, and expected response shape. It is long, but most sentences carry useful behavior or response details that are absent from an output schema, so the length is earned.

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?

Despite having no output schema, the description enumerates the response envelope and key stats, names the input constraints, explains the empty-wallet case, and provides routing guidance. For a one-parameter read-only tool, this is fully actionable.

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 parameter is already described as a base58 Solana wallet address. The description only repeats 'address (base58 wallet)' without adding new semantic constraints or formatting details, so it meets the baseline but adds no extra value.

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 use: judging a new memecoin by the creator's earlier pump.fun launches, and clearly distinguishes it from launch-specific evidence tools. It names the alternatives for launch-level checks, so an agent can differentiate creator_reputation from the launch-check siblings without opening schemas.

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

Usage Guidelines5/5

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

It explicitly says when to use the tool ('before buying') and directs the agent to alternatives ('for the launch's own live evidence use the compact check or the full card'). This provides both a positive trigger and a routing condition, leaving little room for ambiguity.

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

All loophole-tape toolsInspect
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