AgentFeed

Solana network health

get_sol_network

Read-onlyIdempotent

Solana network health: recent average TPS, the current slot, the current epoch and epoch progress in %. Costs 0.005 USDC per call (x402, USDC on Solana, Base, Polygon, Arbitrum or Arc).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	the get_sol_network payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_sol_network
`tool`	Yes	the tool that produced this payload

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": {},
+      "description": "the get_sol_network payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_sol_network",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "tool": {
+      "const": "get_sol_network",
+      "description": "the tool that produced this payload",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "data"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds a genuinely useful behavioral trait beyond the annotations: a per-call cost of 0.005 USDC via x402 with accepted chains, which the agent could not infer from structured fields.

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?

Two sentences, both earning their place: the first front-loads the returned metrics, the second discloses payment terms. No filler or redundancy.

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?

An output schema exists, so return-value documentation is unnecessary, and the description already summarizes the payload plus the cost model. For a zero-param, read-only tool this is complete.

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

Parameters4/5

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

There are zero parameters, so the schema baseline of 4 applies. The description correctly adds no parameter detail because none exists, and there is no ambiguity about inputs.

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 (Solana network health) and enumerates the exact metrics returned: average TPS, current slot, current epoch, and epoch progress %. This clearly separates it from siblings like get_sol_price (price) and get_sol_token_check (token-level), so an agent can identify it 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the metric list but there is no explicit when-to-use, when-not-to-use, or alternative routing (e.g., versus get_priority_fees or get_sol_price for related Solana data). For a zero-param read tool the inference is easy, but the description adds no guidance.

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

All AgentFeed 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.