Skip to main content
Glama

token_risk

Read-only

Risk report for a BNB Chain (bsc) or Base token: honeypot and buy/sell/transfer tax simulation, owner privileges (mint, blacklist, pause, fee changes), upgradeable proxy, liquidity USD, LP burned/locked share, owner holdings, risk score 0-100 with flags. Use before buying or recommending a token.

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": {
      "chain": "<chain>",
      "address": "<address>"
    },
    "name": "token_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesbsc = BNB Chain, base = Base
addressYestoken contract address
api_keyNoNovaquill API key for paid credits (optional; 10 free calls/day without)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds real behavioral context beyond that — it discloses that results come from a honeypot and buy/sell/transfer tax simulation, owner-privilege checks, proxy/upgradeability detection, and a 0-100 score with flags. It omits simulation latency, failure modes, and how flags/score thresholds should be interpreted.

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?

A single dense sentence front-loads the resource and scope, and the long enumeration is a list of concrete report contents rather than filler. The trailing usage clause is short and separately earns its place.

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?

With no output schema, the description carries the burden of describing returns, and it does so by enumerating taxes, privileges, proxy status, liquidity USD, LP lock, owner holdings, and the score. Minor gaps remain around what the 'flags' look like and the response shape, but an agent can call it correctly.

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%, with the chain enum and address pattern fully documented in the schema, so the schema does the heavy lifting. The description only echoes the supported chains and adds no format or usage detail beyond it — baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource ('Risk report for a BNB Chain (bsc) or Base token') and enumerates exactly what the report covers, so an agent can distinguish it from a launch-listing tool like new_launches at a glance.

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 clear context: 'Use before buying or recommending a token,' which tells the agent the decision this tool supports. It does not state exclusions or name alternatives, so it stops short of full routing guidance.

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