loophole-tape

Solana swap builder, 0.25% disclosed fee (free)

swap_build_checked

Read-onlyIdempotent

Free. Use it when you buy or sell a pump.fun token (curve or PumpSwap pool): without wallet an estimated quote (output, impact, fee) from curve or pool reserves; with wallet the UNSIGNED Jupiter swap. Refused on avoid/block. Fee: a disclosed 0.25% (25 bps) to loophole tape's wallet. Holds no keys.

Input Schema

TableJSON Schema

Name	Required	Description
`mint`	Yes	the pump.fun token: a mint or a pump.fun/gmgn/solscan/birdeye link
`side`	Yes	buy or sell, required: amount is in lamports for buy, token base units for sell
`amount`	Yes	whole base units: lamports for buy (max 50 SOL), token base units for sell
`wallet`	No	optional: the signing wallet's base58 key; without it, an estimated quote
`slippage_pct`	No	percent, default 1

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`data`	No
`meta`	No
`coverage`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 3, 2026

changedInput schema / properties / amount / description

Previous value: -"Base units: lamports for buy (10000000 = 0.01 SOL, max 50 SOL), token units for sell (6 decimals)"New value: +"whole base units: lamports for buy (max 50 SOL), token base units for sell"

removedInput schema / properties / amount / maxLength
```
Removed value: -20
```
removedInput schema / properties / amount / minLength
```
Removed value: -1
```

changedInput schema / properties / mint / description

Previous value: -"Token to trade: a mint or a pump.fun/gmgn/solscan/birdeye link"New value: +"the pump.fun token: a mint or a pump.fun/gmgn/solscan/birdeye link"

changedInput schema / properties / side / description

Previous value: -"buy or sell (required): amount is in lamports for buy, token units for sell"New value: +"buy or sell, required: amount is in lamports for buy, token base units for sell"

addedInput schema / properties / side / enum
```
Added value: +[
+  "buy",
+  "sell"
+]
```

changedInput schema / properties / slippage_pct / description

Previous value: -"Percent, default 1, max 5"New value: +"percent, default 1"

changedInput schema / properties / wallet / description

Previous value: -"Base58 public key that signs and receives"New value: +"optional: the signing wallet's base58 key; without it, an estimated quote"

changedInput schema / required

Previous value: -[
-  "mint",
-  "wallet",
-  "amount",
-  "side"
-]New value: +[
+  "mint",
+  "amount",
+  "side"
+]

AddedOct 2, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: the 0.25% / 25 bps disclosed fee destination, the fact that it holds no keys, that the output is an UNSIGNED transaction, and the refusal policy. readOnlyHint=true is consistent with a builder that returns an unsigned tx and mutates no state, so there is no contradiction.

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?

Front-loads 'Free. Use it when...' and every clause carries information (fee, key custody, refusal, mode split). It is dense and semicolon-heavy, bordering on run-on, which costs it the top score.

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 5-parameter tool with an output schema, the description covers the essential context: fee, mode behavior, refusal conditions, and key custody. It leaves 'avoid/block' undefined (presumably a verdict signal from a sibling tool), which is a minor gap rather than a blocker.

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 description coverage is 100%, so the baseline is 3. The description earns extra credit by explaining the semantic split of the optional wallet parameter (quote mode vs. unsigned-swap mode) and the reserve sources used for estimates, which the schema only gestures at.

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?

States a specific verb+resource (build a Solana swap for a pump.fun token) and splits the behavior precisely: quote without a wallet, unsigned Jupiter swap with one. An agent can distinguish it from discovery tools like pumpfun_recent_launches or risk tools like check_pumpfun_risk without opening any schema.

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?

Gives clear triggering context ('when you buy or sell a pump.fun token (curve or PumpSwap pool)') and an exclusion ('Refused on avoid/block'), plus the wallet/no-wallet branching. It does not name a sibling alternative explicitly, so it falls short of the 5 bar.

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

All loophole-tape tools Inspect

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.