Skip to main content
Glama

BRAINIAC Token Due Diligence

Analyze token contract

token-due-diligence_analyze
Read-onlyIdempotent

Analyze a token contract on Base Mainnet including bytecode, ERC-20 metadata, owner, proxy status, and privileges. Price $0.05 USDC. POST /api/v1/token-due-diligence/analyze. 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_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenAddressYestokenAddress, string. Required.

Output Schema

NameRequiredDescriptionDefault
statusNostatus. String.
chainIdNochainId. Number.
sourcesNosources. Array.
analysisNoanalysis. 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.8/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 traits, so the bar is lower; the description nonetheless adds material behavior beyond them: the $0.05 USDC cost and the x402 rule that an unpaid call returns payment terms and does not execute. It does not describe failure modes beyond the payment path, but the output schema carries return shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with capability, then cost and endpoint, then the one precondition that changes agent behavior. Every sentence carries distinct information with no restatement of the schema.

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 one-parameter read tool with full annotations and an output schema, the description covers purpose, chain, cost, endpoint, and the critical paywall behavior. The only material gap is routing guidance against the closely related permissions and security-report siblings.

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?

Single parameter 'tokenAddress' with 100% schema description coverage, so the schema already documents it and the baseline is 3. The description adds only indirect context, that the address should be a Base Mainnet token contract; it gives no format, contract-type, or validation detail beyond the schema's regex pattern.

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?

Specific verb plus resource plus chain scope: 'Analyze a token contract on Base Mainnet,' with an enumerated scope list (bytecode, ERC-20 metadata, owner, proxy status, privileges). That enumeration distinguishes it from holders/liquidity/honeypot siblings, though the overlap with the separate permissions tool is left unaddressed and no sibling is named.

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 chain constraint (Base Mainnet) and the payment precondition implicitly define when the tool is applicable, but there is no explicit when-to-use versus token-due-diligence_security-report or token-due-diligence_permissions, and no stated exclusions. Guidance is implied rather than stated.

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