Skip to main content
Glama

arb_token_risk

Read-onlyIdempotent

GoPlus risk flags (terminal + caution) with a low/medium/high level — Every GoPlus risk flag for an Arbitrum token in one call — terminal (honeypot, can't-sell, self-destruct) and caution (tax, mintable, owner powers, pausable, blacklist, proxy, unverified, weak LP, concentration) — with a low/medium/high level. No GoPlus answer → not charged. Not advice. Required input: address. Priced $0.02 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No API key required.

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

Input Schema

NameRequiredDescriptionDefault
addressYesArbitrum token address

Output Schema

NameRequiredDescriptionDefault
dataNoThe result payload. Shape is service-specific; every field is documented in the tool description.
serviceNoThe service id that answered.
checkedAtNoISO-8601 timestamp of when the underlying reads were taken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, yet the description still adds real value: the terminal-vs-caution taxonomy, the fact that no GoPlus answer means no charge, the x402 $0.02 price, the x-credit-token prepaid path, 1 free call/day, and no API key needed. These are operational facts an agent cannot get from structured fields. It stops short of describing response shape, though an output schema exists, so 4 rather than 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded, but the 'with a low/medium/high level' clause is repeated verbatim, and the payment/logistics sentences take as much space as the tool's actual function. The legal disclaimer and free-tier detail are useful but could be compressed.

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 a one-parameter, read-only tool with an output schema and rich annotations, the description covers what the agent needs: chain scope, flag categories, severity model, billing behavior, and auth. Only the selection story relative to the sibling verdict tools is missing.

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 required parameter and schema coverage is 100%, with the schema already saying 'Arbitrum token address'. The description only restates 'Required input: address' and adds the chain qualifier, which is baseline-level value. A 3 is correct when the schema does the heavy lifting.

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 resource (Arbitrum token) and a specific output (GoPlus risk flags bucketed into terminal and caution categories plus a low/medium/high level). It enumerates the concrete flags it returns, which lets an agent distinguish it from generic siblings like token_risk or arb_token_verdict. It never names an alternative explicitly, 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?

Usage is implied rather than stated: 'in one call' and 'Every GoPlus risk flag' suggest this is the exhaustive-flags tool, but there is no explicit when-to-use versus the sibling verdict tools, and no exclusions. The practical guidance it does give is commercial (billing, free tier) rather than selection 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