Skip to main content
Glama

BRAINIAC Token Due Diligence

Analyze holder concentration

token-due-diligence_holders
Read-onlyIdempotent

Analyze holder concentration from transfer events when complete transfer history is available on Base Mainnet. Price $0.10 USDC. POST /api/v1/token-due-diligence/holders. 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_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
toBlockNotoBlock, integer, from 0 to 9007199254740991. Optional.
fromBlockNofromBlock, integer, from 0 to 9007199254740991. Optional.
tokenAddressYestokenAddress, string. Required.
deploymentBlockNodeploymentBlock, integer, from 0 to 9007199254740991. Optional.

Output Schema

NameRequiredDescriptionDefault
statusNostatus. String.
holdersNoholders. Object.
sourcesNosources. Array.
toBlockNotoBlock. Number.
fromBlockNofromBlock. Number.
result_idNoresult_id. String.
limitationsNolimitations. Array.
received_atNoreceived_at. String.
retrievedAtNoretrievedAt. String.
currentBlockNocurrentBlock. Number.
tokenAddressNotokenAddress. String.
missing_itemsNomissing_items. Array.
scannedBlockRangeNoscannedBlockRange. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: a $0.10 USDC price, the POST endpoint, and the fact that an unpaid call returns x402 payment terms and does not execute. The annotations already cover read-only/idempotent/non-destructive semantics, so the payment and failure-mode disclosure is the real value here; it stops short of describing result shape or cost/accuracy caveats.

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 short sentences, front-loaded with the purpose, then the cost/endpoint, then the unpaid-call behavior. No filler, though the endpoint string and price could be more tightly integrated with the usage statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With rich annotations, a full output schema, and 100% schema description coverage, the description supplies exactly the missing pieces: data precondition, cost, transport, and unpaid-call outcome. Nothing essential for correct invocation is absent.

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%, so the schema documents all four parameters. The description adds no meaning about fromBlock, toBlock, or deploymentBlock (e.g., why deploymentBlock matters for completeness), so baseline 3 applies.

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?

States a specific verb and resource ('Analyze holder concentration from transfer events') and adds a data-availability scope ('complete transfer history on Base Mainnet'). It is clearly distinct from the honeypot/liquidity/permissions siblings, though it does not explicitly name or contrast with them.

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 concrete precondition for use: only when complete transfer history is available on Base Mainnet. It does not name an alternative for partial-history cases or state explicit exclusions, so it falls short of a full when/when-not routing statement.

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