Skip to main content
Glama

BRAINIAC Token Due Diligence

Check honeypot status

token-due-diligence_honeypot
Read-onlyIdempotent

Check if a token is a honeypot using Honeypot.is simulation, including buy/sell tax, gas information, and contract verification. Price $0.05 USDC. POST /api/v1/token-due-diligence/honeypot. 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-due-diligence_honeypot"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairAddressNopairAddress, string. Optional.
tokenAddressYestokenAddress, string. Required.

Output Schema

NameRequiredDescriptionDefault
statusNostatus. String.
sourcesNosources. Array.
honeypotNohoneypot. Object.
result_idNoresult_id. String.
limitationsNolimitations. Array.
received_atNoreceived_at. String.
retrievedAtNoretrievedAt. String.
tokenAddressNotokenAddress. String.
missing_itemsNomissing_items. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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 semantics. The description adds genuinely new behavioral context: the $0.05 USDC cost, the POST endpoint, and crucially that an unpaid call returns x402 payment terms without running the simulation — a detail an agent cannot get from structured fields.

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?

Three tight sentences, front-loaded with the core purpose followed by cost and payment behavior. The endpoint path borders on redundant with the tool name but is useful for API-level consumers; nothing is padding.

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?

With an output schema present, return values need not be described, and the definition still covers cost, transport, and the failure mode for unpaid calls. The only gap is guidance on the optional pairAddress and on alternatives among the sibling due-diligence 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 description coverage is 100% with only two parameters, so the schema already documents tokenAddress as required and pairAddress as optional. The description adds no meaning about what pairAddress affects or when to supply it, so it sits at the baseline.

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?

Names a specific verb and resource ('Check if a token is a honeypot') and enumerates the returned signals (buy/sell tax, gas, contract verification). It is clearly distinct from siblings like holders, liquidity, and permissions, though it does not explicitly name which sibling covers adjacent concerns.

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: an agent infers it should call this when screening a token for honeypot risk. There is no explicit statement about when to prefer security-report or analyze instead, and no prerequisites beyond the payment note.

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