Skip to main content
Glama

Wallet Doctor

tokenSafety

Read-only

Token mint safety: mint/freeze authority, supply, decimals; top-10 holder concentration when the public RPC allows it — $0.001 USDC per call via x402 v2 (Solana or Base).

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": {
      "mint": "<mint>"
    },
    "name": "tokenSafety"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Goes beyond readOnlyHint/openWorldHint by disclosing the exact checks performed, the conditional limitation for holder concentration, per-call pricing via x402 v2, and supported networks. It omits return shape and failure behavior when the public RPC is unavailable.

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?

Delivered in one tight sentence with the core purpose front-loaded and payment/network details compactly appended. No filler or redundant restatement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a one-parameter read-only check because it names the data returned and the payment/network context. However, with no output schema and no schema parameter documentation, it should explain the mint input more and give at least minimal response-shape or RPC-failure context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage and a single required 'mint' parameter. The description only implies 'mint' means a token mint and does not specify address format, chain selection, or constraints, so it adds little parameter-level meaning.

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 it checks token mint safety and enumerates mint/freeze authority, supply, decimals, and top-10 holder concentration. Specific enough to identify the resource, but it does not explicitly contrast with siblings such as drainForensics or txtrace, so differentiation is left implicit.

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?

Implies the use case as assessing a token mint's safety and notes the public-RPC dependency and supported chains/payment model. It does not say when to choose this over sibling tools or what preconditions apply beyond payment and RPC availability.

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