Skip to main content
Glama

sol_token_risk

Read-onlyIdempotent

RugCheck risk score (0–100) + the flags behind it — A single risk score (0 = clean … 100 = max risk) for any SPL mint, with the danger flags and warnings behind it, from RugCheck. Low/medium/high band for a quick gate. If RugCheck does not answer, you are not charged. Not advice. Required input: mint. 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": {
      "mint": "<mint>"
    },
    "name": "sol_token_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesSolana SPL mint 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, so safety is covered. The description adds genuinely non-inferable behavior: the $0.02/call x402 pricing on Base, the prepaid x-credit-token alternative, 1 free call/day, and that a non-response from RugCheck is not charged. That failure/payment guarantee is the kind of detail annotations cannot carry. Missing: score scale behavior on partial data or timeouts other than billing.

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, which is good, but the sentence sprawls through em-dashes and repeats itself ('the flags behind it' and 'the danger flags and warnings behind it'). Payment mechanics are interleaved with capability description rather than separated, making the definition noisier than its content requires.

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?

An output schema exists, so return-value explanation is not needed, and the description covers cost, payment paths, failure billing, and the 'not advice' disclaimer. For a single-parameter read tool this is nearly sufficient; what is missing is any note on latency or how partial/unknown results surface in the score.

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 'mint' parameter, including its meaning ('Solana SPL mint address'). The description only restates 'Required input: mint' and adds nothing about format, address validation, or cross-chain ambiguity. Baseline 3 is appropriate when the schema already does the work.

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 verb and resource: a 0–100 risk score plus the danger flags and warnings behind it, scoped to 'any SPL mint' and attributed to RugCheck. An agent knows exactly what it gets back conceptually. It does not name a sibling (e.g. token_risk, sol_token_verdict) to draw the boundary, so it stops one step 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?

'Low/medium/high band for a quick gate' implies a screening use case, which is real guidance. However, there is no explicit when-not, no mention of when to prefer a deeper sibling like sol_token_verdict or sol_sellability, and no prerequisites beyond the required mint. Usage is implied rather than prescribed.

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