Skip to main content
Glama

BRAINIAC Token Due Diligence

Generate security report

token-due-diligence_security-report
Read-onlyIdempotent

Generate a combined security report using Honeypot checks. Price $0.10 USDC. POST /api/v1/token-due-diligence/security-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-due-diligence_security-report"
  }
}

Input Schema

NameRequiredDescriptionDefault
pairAddressNopairAddress, string. Optional.
tokenAddressYestokenAddress, string. Required.
includeHoneypotNoincludeHoneypot, boolean. Required.
includeMarketActivityNoincludeMarketActivity, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
statusNostatus. String.
sourcesNosources. Array.
findingsNofindings. 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?

Beyond the annotations, it discloses the two facts an agent most needs: the call costs $0.10 USDC, and an unpaid call returns x402 payment terms without executing. That payment-gating behavior is exactly the kind of context annotations cannot convey. It does not cover rate limits, latency, or what the report contains, keeping it below a 5.

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 short sentences: what it does, what it costs, and what happens when payment is missing. The payment caveat is placed where an agent will read it before deciding to call, and nothing is redundant.

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?

An output schema exists, so return values need no explanation, and the payment path is fully described. The remaining gap is guidance on choosing this aggregated report over the sibling single-check tools, which matters given five closely related alternatives.

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% and all four parameters carry descriptions and patterns, so the schema does the heavy lifting. The description adds only the hint that Honeypot checks are involved, implying includeHoneypot, but says nothing about tokenAddress, pairAddress, or includeMarketActivity. 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 ('Generate a combined security report using Honeypot checks'), and the word 'combined' signals it aggregates multiple checks rather than the single-purpose siblings like honeypot, liquidity, or holders. It stops short of naming which siblings it supersedes, so differentiation is implied rather than explicit.

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 word 'combined' implies you should pick this over the individual per-check tools when you want everything at once, but the description never states that condition or any exclusions. No prerequisites beyond the payment note are given, so the agent must infer when to prefer this over token-due-diligence_honeypot or _analyze.

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