QuickBuild token-saver tools + x402

sol_token

Read-onlyIdempotent

[PAID $0.003 USDC per call via x402 on Base; errors are free] Mint account read live from the public Solana mainnet RPC (jsonParsed). Every response has disclaimer: "informational only, not investment advice"; unavailable values are null (never invented). Not a mint = 404, invalid = 400, never charged.

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

Input Schema

Name	Required	Description	Default
`mint`	No	base58 SPL mint address (default USDC)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond the annotations, it discloses paid pricing, error-free charging, the live public RPC data source, a mandatory disclaimer, null-not-invented semantics, 404/400 error mapping, and 'never charged' behavior. This is rich, actionable behavioral context that an agent could not infer from the annotations alone.

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?

The description is compact and every clause carries useful information: cost, data source, disclaimer, null semantics, and error charging. It is dense with semicolons and places payment terms before the core action, which slightly reduces front-loading of purpose.

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 one-optional-parameter read-only tool, the description covers cost, data source, disclaimer, unavailable-value handling, and error statuses. With annotations covering safety and idempotency and no output schema, this is sufficient for correct invocation without over-specifying.

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%, and the schema already documents the mint parameter as a base58 SPL mint address defaulting to USDC. The description does not add syntax, format, or default details beyond the schema, so the baseline 3 applies.

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?

The description states a specific resource and action: reading a Solana mint account live from the public mainnet RPC in jsonParsed form. The chain and resource distinguish it from base_token_info and sol_wallet, though it never explicitly names or contrasts those siblings.

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 by 'Mint account read live' but the description does not state when to choose this over alternatives such as base_token_info or sol_wallet. It gives error behavior but no selection guidance or exclusions.

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

All QuickBuild token-saver tools + x402 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?