Skip to main content
Glama

BRAINIAC Token Security & Risk Intelligence

Deployer funding and holder clusters

token-security_deployer-funding-trace
Read-onlyIdempotent

Identify the Base token deployer, walk early inbound funding hops, and report holder concentration clusters. Unknown funding origin is identified=false with origin_label=unknown — not a neutral skip. Price $0.10 USDC. POST /api/v1/token-security/deployer-funding-trace. 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_deployer-funding-trace"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxHopsNomaxHops, integer, from 1 to 5. Required.
topHoldersNotopHolders, integer, from 1 to 50. Required.
tokenAddressYestokenAddress, string. Required.

Output Schema

NameRequiredDescriptionDefault
statusNostatus. String.
sourcesNosources. Array.
clustersNoclusters. Array.
deployerNodeployer. String.
result_idNoresult_id. String.
identifiedNoidentified. Boolean.
limitationsNolimitations. Array.
received_atNoreceived_at. String.
retrievedAtNoretrievedAt. String.
funding_pathNofunding_path. Array.
origin_labelNoorigin_label. String.
tokenAddressNotokenAddress. String.
missing_itemsNomissing_items. Array.
max_cluster_share_pctNomax_cluster_share_pct. Number.

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?

Beyond the annotations, it discloses cost ($0.10 USDC), the endpoint, and critical x402 behavior: an unpaid call returns payment terms and does not execute. It also explains that an unknown funding origin sets identified=false and origin_label=unknown rather than being treated as a neutral skip.

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?

The purpose is front-loaded and the payment and unknown-origin semantics are compact. Each sentence carries relevant information, though the explicit endpoint is somewhat redundant for an agent already invoking the tool.

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?

Annotations cover read-only, idempotent, open-world, and non-destructive behavior, an output schema exists for return values, and parameters are fully described in the schema. The description adds payment and unknown-origin handling, leaving little material ambiguity for a three-parameter tracing tool.

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%, so maxHops and topHolders are already documented structurally. The description only loosely connects 'early inbound funding hops' to maxHops and 'holder concentration clusters' to topHolders, adding little beyond the schema.

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 uses specific verbs and resources: identify the Base token deployer, walk early inbound funding hops, and report holder concentration clusters. It is clearly distinguishable from siblings such as honeypot, liquidity, ownership, and sell simulation, although it does not name any alternative explicitly.

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 scope is clear: Base tokens and deployer funding lineage plus holder concentration. There is no explicit when-to-use or when-not-to-use guidance against the sibling risk tools, so the agent must infer the appropriate context.

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