MAD Synapse

Solana network status

solana_network

Read-onlyIdempotent

Solana right now: TPS (total and non-vote), slot and block height, epoch progress and ETA, priority-fee percentiles, cluster version. Read from mainnet RPC: recent performance samples, epoch info, prioritization fees. When to use: For Solana fees/TPS; for EVM and BTC fee costs use gas_now (callable here by name). Price: free. Errors: returns isError with a message for invalid input or an upstream failure (not charged).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`slot`	No
`epoch`	No
`version`	No
`tps_total`	No
`avg_slot_ms`	No
`block_height`	No
`tps_non_vote`	No
`window_minutes`	No
`epoch_progress_pct`	No
`epoch_ends_in_hours`	No
`priority_fee_micro_lamports_per_cu`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "avg_slot_ms": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "block_height": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "epoch": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "epoch_ends_in_hours": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "epoch_progress_pct": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "priority_fee_micro_lamports_per_cu": {
+      "properties": {
+        "non_vote_txs_sampled": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "p25": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "p50": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "p75": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "p90": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "share_paying_no_priority_pct": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "slot_sampled": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "slot": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "tps_non_vote": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "tps_total": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "version": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "window_minutes": {
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

AddedSep 26, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds genuinely new context: data provenance (mainnet RPC performance samples, epoch info, prioritization fees), cost (free), and error behavior (isError returned for invalid input or upstream failure, not charged). That is meaningful beyond the annotations, though it says nothing about caching/staleness of 'right now'.

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 resource ('Solana right now') followed by the return payload, then usage, cost, and errors in a compact run of clauses. Dense but every clause carries information; the semicolon-chained list is slightly harder to scan than separate sentences.

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 values need no explanation, and annotations cover the safety profile. Combined with the description's coverage of source, cost, and failure modes, an agent has everything needed to call this zero-arg tool correctly.

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?

The tool takes zero parameters, so per the rubric the baseline is 4. There is nothing further for the description to disambiguate 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 status) and enumerates exactly what it returns: TPS total and non-vote, slot/block height, epoch progress and ETA, priority-fee percentiles, cluster version. It also names the sibling it is not (gas_now for EVM/BTC fees), so an agent can distinguish it without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit 'When to use' clause scoped to Solana fees/TPS, with the alternative (gas_now) named by tool name for the EVM/BTC case. This is textbook routing guidance with no inference required.

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

All MAD Synapse 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?