Skip to main content
Glama
Sign In

Tereno on Base

by xyz.tereno
OverviewDiscussionsAdmin

Can I get out after I get in? Base token launch & honeypot guard

token_launch_guard

Can I get out after I get in? Simulate a real buy and sell against a freshly launched Base token, read the owner powers left in its bytecode, and return both with the block they stop being true at. Paid per call with x402 on Base: $0.02 to $0.07 USDC depending on how much of the answer the network already has. Shared: reusing an answer another agent already paid for costs less, and the wallet that produced it earns a bounded credit.

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": {
      "address": "<address>"
    },
    "name": "token_launch_guard"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesBase token address to check before buying: simulates sell/exit via eth_call, verifies DEX LP reserves and burn/lock status, and inspects owner powers (mint, blacklist, pause, fee traps). Includes 1 free daily check per IP for testing; unlimited calls via x402 or prepaid tokens.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses x402 pricing tiers ($0.02–$0.07 USDC), a shared-answer discount, a bounded credit to the producing wallet, and that results carry a block at which they stop being true. It does not explicitly state that the simulation is read-only and makes no state changes, which is the main remaining gap.

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 lead question front-loads the value proposition, followed by what it does and then cost mechanics. The pricing sentence is long but each clause carries distinct information; nothing is redundant.

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?

No output schema exists, and the description does explain the shape of the return: a buy/sell simulation result, owner powers, and a validity block. For a single-parameter read tool this is nearly complete, though it could say more about failure modes for non-token addresses.

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 thoroughly documented in the schema itself, so the description adds little beyond identifying it as a Base token address to check before buying. Baseline 3 applies when the schema does the heavy lifting.

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 specific verbs and resources: simulate a buy and sell against a freshly launched Base token, read owner powers from bytecode, and return both with a validity block. This is clearly distinguishable from siblings like contract_guard and token_metadata.

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

Usage Guidelines3/5

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

The framing question and 'before buying' context imply when to use it, but the description never names an alternative or states exclusions versus contract_guard or token_metadata. Usage is implied rather than explicit.

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

All Tereno on Base 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