Skip to main content
Glama

loophole-tape

by io.github.gosadu
OverviewDiscussionsAdmin

Outcome labels for up to 40 pump.fun memecoins ($0.01)

mint_outcome_batch
Read-onlyIdempotent

$0.01 USDC per call, whatever the answers. Use when you grade a list of your own rug or graduation calls or backtest a signal on pump.fun memecoins; for one mint the $0.001 single lookup costs less. Input: mints (an array of one to 40 distinct pump.fun mints, each a mint or a pump.fun/gmgn/solscan/birdeye link). One payment returns the outcome labels of one to 40 caller-selected pump.fun mints in the order asked with the fields and the fixed public rule of the single lookup GET /v1/outcome/{mint} and is charged once whatever the answers. Each item: rugged by the public rule and when, rugged within 300 s of launch, true graduation and migration time, the creator's first sell, peak and last curve SOL, the mayhem flag, whether each label is settled (resolved) and the rule version. A mint we never saw answers known:false. More than 40, a malformed or a repeated mint is refused unpaid. No probabilities and no opinions. Returns a JSON envelope with data{count, n_known, n_resolved, items[the single tool's fields, in the order asked], rule}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mintsYesOne to 40 distinct pump.fun mints, each a mint or a pump.fun/gmgn/solscan/birdeye link, known to our capture or not.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / mints / description
      Previous value: -"One to 40 distinct pump.fun mints, known to our capture or not."New value: +"One to 40 distinct pump.fun mints, each a mint or a pump.fun/gmgn/solscan/birdeye link, known to our capture or not."
    • addedInput schema / properties / mints / items / description
      Added value: +"a mint or a pump.fun/gmgn/solscan/birdeye link"
    • changedInput schema / properties / mints / items / maxLength
      Previous value: -44New value: +512
    • removedInput schema / properties / mints / items / pattern
      Removed value: -"^[1-9A-HJ-NP-Za-km-z]{32,44}$"
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds valuable behavioral context: charged once regardless of outcomes, known:false for unseen mints, no probabilities/opinions, and the exact response envelope structure. It exceeds what annotations alone provide.

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 long but densely packed with necessary details: pricing, use case, input format, return fields, and edge cases. It front-loads cost and purpose, and every sentence contributes information. While not terse, the complexity of a batch tool justifies the length.

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?

With an output schema and strong annotations, the description still provides complete context: pricing, exact input rules, return envelope structure, field list, rule version, and handling of unknown mints. An agent has everything needed to invoke this tool correctly and interpret results.

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 covers the only parameter (mints) 100%, so baseline is 3. The description adds extra semantic constraints: refusal for >40, malformed, or repeated mints, and that each item can be a mint or a link. This goes beyond schema and clarifies expected input validation behavior.

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 clearly states the tool's purpose: providing outcome labels for up to 40 pump.fun memecoins for $0.01, explicitly for grading rug/graduation calls or backtesting. It distinguishes from the single lookup sibling by price and batch size, making it unambiguous which tool to choose.

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 states when to use this batch tool (grading lists or backtesting) and when not to (single mint costs less with the single lookup). It also specifies input constraints (1-40 mints) and refusal conditions (more than 40, malformed, or repeated) — clear, actionable guidance with alternatives.

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