Token Safety (Base)

by dev.workers.restockalarm.token-safety-mcp

holder_check

holder_check

Read-only

PAUSED: holder_check answers paused without asking for payment and is never charged (its top-holder source was a third-party API we no longer use). For holder concentration use token_risk (holder_concentration).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "holder_check"
  }
}

Input Schema

Name	Required	Description	Default
`address`	No	ERC-20 contract address on Base (0x + 40 hex). Tool calls are paid via x402 with or without it; if omitted, the paid call returns the AERO example with example=true. Free look without payment: GET https://token-risk.restockalarm.workers.dev/v1/preview.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

changedInput schema / properties / address / description

Previous value: -"ERC-20 contract address on Base (0x + 40 hex). If omitted, the AERO example is returned with example=true."New value: +"ERC-20 contract address on Base (0x + 40 hex). Tool calls are paid via x402 with or without it; if omitted, the paid call returns the AERO example with example=true. Free look without payment: GET https://token-risk.restockalarm.workers.dev/v1/preview."

First observedOct 19, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds genuinely new behavior: the tool is paused, requires no payment, incurs no charge, and lost its upstream data source. The only friction is that the input schema still describes x402 payment semantics, which sits in mild tension with "never charged" — that is a schema inconsistency rather than an annotation contradiction.

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?

Two sentences, front-loaded with the operative word "PAUSED" so an agent sees the deprecation before anything else. The parenthetical about the retired third-party API is slightly expendable but usefully explains why the pause exists.

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?

For a paused, single-optional-parameter read tool with no output schema, this is close to complete: the agent learns to avoid paying a call and is routed to the correct sibling. Only the original purpose of the tool remains unstated.

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% for the single address parameter, including the regex pattern and the no-payment fallback behavior, so the schema already does the work. The description adds no extra meaning about the address argument, matching the baseline of 3.

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

Purpose3/5

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

The description leads with "PAUSED" and mentions "its top-holder source," which hints at a holder-distribution analyzer, but it never states a clear verb+resource for what holder_check originally returned. Its main virtue is distinguishing itself from token_risk, so an agent knows immediately this is not the tool it wants.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when-not-to-use (the tool is paused), a cost guarantee ("answers paused without asking for payment and is never charged"), and a named alternative with the specific capability to use instead: "For holder concentration use token_risk (holder_concentration)." Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Token Safety (Base) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?