Skip to main content
Glama

loophole-tape

by io.github.gosadu
OverviewDiscussionsAdmin

Solana wallet profile ($0.02)

wallet_profile
Read-onlyIdempotent

$0.02 USDC per call. Use to classify a wallet buying a pump.fun memecoin (insider, latency_bot or skilled) and read its realised PnL when it ranks on our leaderboard; it describes the wallet, not a mint's rug risk (use GET /v1/check/mint). Input: address (base58 wallet). An unranked wallet gets a null class and no PnL. A ranked wallet carries its class and rank with stats (realised PnL in SOL, win rate, positions) from our realised-PnL leaderboard over the pump.fun trades we captured (window and build time in the response); every wallet gets its holdings among the last 3000 mints (token share, first-buy slot, curve SOL now), creator stats if it ever launched, and its recent funding source. Use it to weight the buyers on a curve. Returns JSON envelope with data{wallet, leaderboard{class, rank, stats}, as_creator, live_holdings_recent_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?

Annotations already flag readOnly/open-world/idempotent, so behavior is safe. The description adds valuable behavioral detail: per-call pricing, the distinction between ranked and unranked wallets, null class behavior, the leaderboard window/build time, holdings among last 3000 mints, creator stats, and funding source. There is no contradiction with the annotations.

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 packed with necessary detail given there is no output schema. It front-loads the price and core purpose, then covers output fields, ranked/unranked distinctions, holdings, creator stats, and funding source. Some sentences are dense and run-on, but no sentence is wasted.

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 one-parameter read-only tool with no output schema, the description carries the full burden of explaining the response structure and edge cases. It covers what is returned, the ranked/unranked distinction, the leaderboard window, holdings, creator stats, funding source, and even cost. Agents have enough to select and invoke 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 coverage is 100%, with the 'address' parameter already documented as a base58 Solana wallet address (32-44 chars). The description reinforces 'Input: address (base58 wallet)' and ties it to the wallet-profile behavior, but adds little meaning beyond the schema. The baseline of 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?

The description states a specific verb and resource: 'classify a wallet buying a pump.fun memecoin' and 'read its realised PnL'. It also explicitly differentiates itself from mint-level risk assessment by directing to 'GET /v1/check/mint', making it distinguishable from sibling risk-check tools.

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 gives an explicit intended use case: 'Use to classify a wallet' and 'Use it to weight the buyers on a curve'. It also names the alternative for mint rug risk, telling the agent when not to use this tool. This leaves little to inference.

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