Skip to main content
Glama

BRAINIAC Token Security & Risk Intelligence

Honeypot risk check

token-security_honeypot-risk-check
Read-onlyIdempotent

Look for observable pause and blacklist indicators in Base bytecode and standard calls. This does not simulate a buy or sell. Price $0.04 USDC. POST /api/v1/token-security/honeypot-risk-check. 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_honeypot-risk-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenAddressYestokenAddress, string. Required.

Output Schema

NameRequiredDescriptionDefault
statusNostatus. String.
chainIdNochainId. Number.
sourcesNosources. Array.
findingsNofindings. Array.
result_idNoresult_id. String.
assessmentNoassessment. String.
limitationsNolimitations. Array.
received_atNoreceived_at. String.
retrievedAtNoretrievedAt. String.
tokenAddressNotokenAddress. String.
missing_itemsNomissing_items. Array.
approvesInteractionNoapprovesInteraction. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive traits, yet the description still adds material behavior: a $0.04 USDC price, the POST endpoint, and the crucial fact that an unpaid call returns x402 payment terms and does not execute. The static-analysis limitation (no buy/sell simulation) is also disclosed, which an agent needs to interpret confidence in the result.

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 short sentences with the purpose front-loaded and the exclusion immediately after it; nothing is padded. The raw endpoint path is mildly redundant for an MCP consumer but is a single clause.

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 values need no explanation, and the description covers what is checked, what is not, cost, and payment behavior. It could go slightly further on what the indicators mean for confidence, but nothing an agent needs to call it correctly is missing.

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?

With a single required parameter at 100% schema description coverage, the schema already carries the semantics. The description adds no format, chain-assumption, or validation detail about tokenAddress beyond what the schema provides, so baseline 3 applies.

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 and resource: looking for observable pause and blacklist indicators in Base bytecode and standard calls. It also bounds the scope ('does not simulate a buy or sell'), which cleanly separates it from the sell-simulation sibling without needing the 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 a clear when-not ('This does not simulate a buy or sell'), which implicitly routes simulation work elsewhere. It stops short of naming the alternative tool or stating positive preconditions for using this one, so it falls short of full when/when-not/alternatives 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