Skip to main content
Glama

YRUZ Solana Token Check (0.005 USDC)

solana_token_check
Read-onlyIdempotent

Safety check of any Solana token before an agent buys it: name, symbol, supply, decimals, token program and extensions, mint and freeze authority, mutable metadata, top-10 holder concentration, holder count, price, liquidity, market cap, organic volume and verification. Returns a 0-100 risk score with every red flag explained. On-chain data from Helius, market data from Jupiter. Price: 0.005 USDC per call, paid with x402 (USDC on Base or Solana, no account, no API key); invalid input is refused before payment and a failed run is never charged. Without a payment the tool returns the x402 PaymentRequired. How to call it: get_example {"tool":"solana_token_check"}. Same tool over HTTP: https://yruz.one/api/crypto/token?mint=JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN

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": "solana_token_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesSolana token mint address (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / mint / examples
      Added value: +[
      +  "JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses the 0.005 USDC price, the x402 payment mechanism, that no account or API key is needed, that failed runs are never charged, and that an unpaid call yields PaymentRequired. It also names the upstream data sources (Helius, Jupiter) and the output shape (0-100 risk score plus explained flags).

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?

Dense but front-loaded: purpose, output, sources, then pricing/payment mechanics. The trailing HTTP endpoint and get_example pointer are useful for the paid-call workflow but make the block slightly sprawling for a one-parameter tool.

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

Completeness5/5

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

For a paid, single-param tool with no output schema, the description covers input, return contents, data sources, cost, payment flow, billing failure semantics, and a pointer to a call example — nothing an agent needs to invoke it successfully 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?

Schema coverage is 100%, so the single 'mint' parameter is already fully documented in the schema. The description reinforces that any Solana token mint works and the HTTP example URL confirms the format, but adds no syntax or validation detail beyond the schema — 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 ('Safety check of any Solana token') and enumerates exactly what is inspected (authorities, holder concentration, liquidity, risk score). This clearly separates it from siblings like crypto_price or solana_portfolio, which do not assess risk.

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?

'before an agent buys it' establishes the decision context clearly, and invalid input being refused pre-payment tells the agent what preconditions matter. It stops short of naming alternative siblings or stating when not to use it.

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.