Skip to main content
Glama

BRAINIAC Token Security & Risk Intelligence

Token risk verdict

token-security_risk-verdict
Read-onlyIdempotent

Read a Base token contract and return an evidence-based verdict. Facts, signals, and unavailable checks are separate. No risk score is produced, and absence of a signal is not a safety approval. Price $0.05 USDC. POST /api/v1/token-security/risk-verdict. 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_risk-verdict"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenAddressYestokenAddress, string. Required.

Output Schema

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses that facts, signals, and unavailable checks are returned separately, that no composite score is computed, and that missing signals are not an approval — all interpretation-critical behavior. It also states the cost ($0.05 USDC), the HTTP endpoint, and that an unpaid call returns x402 payment terms without executing, which is exactly the operational context an agent needs for a paid tool.

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 in the first sentence, followed by interpretive constraints and then operational details (price, endpoint, payment gate). Every sentence carries information, though the endpoint/price clause reads slightly like boilerplate and could be trimmed in a longer doc.

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?

An output schema exists, so return values need not be described, and the description covers the remaining gaps an agent would have: the absence of a risk score, the separation of facts vs. signals vs. unavailable checks, the cost, and the unauthenticated-call behavior.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents tokenAddress and its pattern. The description only indirectly adds that the address must be a Base-chain token contract, which is marginal added meaning — the baseline of 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?

The description names a specific verb and resource ('Read a Base token contract and return an evidence-based verdict') and scopes it to the Base chain, which distinguishes it from the single-signal siblings such as honeypot-risk-check or liquidity-risk-assessment. It does not explicitly contrast itself with those siblings, but the aggregate 'verdict' framing is clear enough to select it.

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?

Usage context is implied by the verdict/no-risk-score framing, but there is no explicit statement of when to pick this over the individual signal tools in the sibling set, nor any prerequisite guidance beyond the payment note. An agent must infer that this is the aggregate option.

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