Skip to main content
Glama

BRAINIAC Token Security & Risk Intelligence

Token sell simulation

token-security_sell-simulation
Read-onlyIdempotent

Simulate buy then sell for a Base token via Honeypot.is and return sellable as pass, fail, or not_checked with buy/sell tax when reported. Absence of a honeypot flag is never recorded as pass without a successful simulation. Price $0.05 USDC. POST /api/v1/token-security/sell-simulation. An unpaid call returns the x402 payment terms and does not run.

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": {
      "tokenAddress": "<tokenAddress>"
    },
    "name": "token-security_sell-simulation"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountUsdNoamountUsd, number, from any to 10000. Required.
pairAddressNopairAddress, string. Optional.
tokenAddressYestokenAddress, string. Required.

Output Schema

NameRequiredDescriptionDefault
poolNopool. String.
routerNorouter. String.
statusNostatus. String.
sourcesNosources. Array.
sellableNosellable. String.
amountUsdNoamountUsd. Number.
amount_inNoamount_in. Null.
result_idNoresult_id. String.
amount_outNoamount_out. Null.
buy_tax_pctNobuy_tax_pct. Number.
limitationsNolimitations. Array.
received_atNoreceived_at. String.
retrievedAtNoretrievedAt. String.
block_numberNoblock_number. Null.
sell_tax_pctNosell_tax_pct. Number.
tokenAddressNotokenAddress. String.
missing_itemsNomissing_items. Array.
revert_reasonNorevert_reason. Null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Well beyond the annotations, the description discloses the upstream provider (Honeypot.is), the exact cost ($0.05 USDC), the transport endpoint (POST /api/v1/token-security/sell-simulation), and crucially that an unpaid call returns x402 payment terms and does not execute. It also defines the semantics of the three possible outcomes and the anti-false-positive rule, which is exactly the behavioral context an agent needs before trusting a 'pass'.

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?

Four dense sentences, front-loaded with the action and result semantics before the commercial and transport details. Every sentence carries information, though the payment sentence is compact enough to read as a run-on and could be split for scannability.

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?

An output schema exists, so return-value structure need not be spelled out, yet the description still usefully defines the pass/fail/not_checked vocabulary and the failure rule. Cost, payment gating, provider, and chain scope are all covered; the only meaningful gap is how the simulated amount interacts with the outcome, plus no explicit routing against the neighboring risk tools.

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 each parameter already carries a description, so the baseline is 3. The description adds no meaning about tokenAddress, pairAddress, or amountUsd — notably it never explains what the simulated trade size (amountUsd, default 100) implies for slippage/liquidity-sensitive results, which is the one place prose would have added real value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb chain and resource: 'Simulate buy then sell for a Base token via Honeypot.is', with a stated result vocabulary (pass/fail/not_checked). It is clearly more than a restated title, but it never names or contrasts with the nearest sibling (token-security_honeypot-risk-check) or the other risk tools, so an agent must infer the boundary between 'simulation' and 'honeypot flag'.

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?

Usage is only implied: the tool is for determining whether a token can actually be sold after buying. There is no explicit when-to-use / when-not-to-use statement and no pointer to the cheaper honeypot-risk-check or risk-verdict siblings that an agent would otherwise need to choose between. The one actionable rule given ('absence of a honeypot flag is never recorded as pass without a successful simulation') is a correctness guarantee, not selection guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources