ScorpTech x402 API

Sol Network

sol_network

Read-onlyIdempotent

Solana mainnet status in one call: current slot and block height, epoch with progress % and estimated time to the next epoch, average slot time, total and non-vote TPS from recent performance samples, node software version, total and circulating SOL supply, and the current inflation rate. Public Solana RPC, read-only. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/sol-network

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_network"
  }
}

Input Schema

Name	Required	Description	Default
`samples`	No	Recent 60-second performance samples averaged for TPS and slot time (1-60)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/destructive-free, and the description adds genuinely new context: a public Solana RPC, mainnet-only scope, and a paid x402 call at $0.002 USDC per successful call — cost/payment semantics an agent must know. It stops short of describing rate limits, error behavior, or what happens on a failed call (no charge).

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?

Front-loaded with the core statement, then the enumerated metrics, then access/pricing notes — no filler. The metric list is long but each item carries information an agent needs since there is no output schema.

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?

With no output schema, the description carries the burden of describing return values and does so exhaustively (slot, height, epoch progress, TPS variants, version, supply, inflation). Access path, cost, and read-only nature are also covered, so an agent has everything needed to call and interpret it.

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?

There is one optional parameter and the schema already documents it at 100% coverage (1–60, 60-second samples averaged for TPS/slot time). The description does not mention 'samples' at all, so it adds no meaning beyond the schema; baseline 3 applies.

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?

States a specific resource and scope ('Solana mainnet status in one call') and enumerates exactly the metrics returned — slot, block height, epoch progress, TPS, supply, inflation. An agent can distinguish it from the sibling sol_* tools (sol_balance, sol_validators, sol_priority_fees) without opening the schema.

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?

'Solana mainnet status in one call' plus the field list makes the intended use case clear, and the HTTPS URL offers an alternative access path. However, it never states when to prefer a sibling such as sol_priority_fees or sol_validators, nor any exclusions or prerequisites.

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

All ScorpTech x402 API 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?