Skip to main content
Glama

BRAINIAC Token Security & Risk Intelligence

Token due diligence report

token-security_due-diligence-report
Read-onlyIdempotent

Combine the Base contract checks and DEX Screener observations into one report for an agent. The report never approves interaction and does not turn missing evidence into a safety claim. Price $0.12 USDC. POST /api/v1/token-security/due-diligence-report. 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_due-diligence-report"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenAddressYestokenAddress, string. Required.

Output Schema

NameRequiredDescriptionDefault
agentNoagent. Object.
tokenNotoken. Object.
checksNochecks. Object.
statusNostatus. String.
chainIdNochainId. Number.
sourcesNosources. 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/5.0
Behavior5/5

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds important context beyond those annotations: the $0.12 USDC price, the POST endpoint, the x402 payment terms returned by an unpaid call, and the fact that unpaid calls do not run. It also discloses advisory limitations, including that the report never approves interaction and does not convert missing evidence into a safety claim.

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?

The description front-loads the core purpose, then adds safety, pricing, endpoint, and unpaid-call behavior without filler. Each sentence contributes operational information an agent needs. It is appropriately sized for a paid, read-only reporting endpoint.

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?

Given the output schema and rich annotations, the description supplies the remaining critical context: cost, payment behavior for unpaid calls, and advisory limitations. It is nearly complete for invocation decisions. The main gap is that it does not explicitly position this aggregate report against the more granular sibling checks.

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?

The single parameter, tokenAddress, is fully described in the schema with a required flag and address pattern. The description adds no further meaning about the parameter, such as examples or chain-specific caveats. With 100% schema coverage, the baseline score of 3 is appropriate.

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 states a specific verb and resources: it combines Base contract checks and DEX Screener observations into one agent-facing report. That makes the aggregate-report purpose clear. It does not explicitly name or contrast against the individual check sibling tools, so it falls short of a 5.

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 implied usage is to obtain a consolidated report rather than running individual checks, and the description notes payment is required. However, it gives no explicit when-to-use, when-not-to-use, or named alternative guidance. The guidance is therefore present only by implication.

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