AgentFeed

Solana priority fees

get_priority_fees

Read-onlyIdempotent

Solana priority fees right now: percentiles from min to max of the per-slot minimum fee paid on the busiest SOL/USDC pools over the last ~150 slots, in micro-lamports per compute unit, with a recommended level. For bots that need their transactions to land. 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_priority_fees payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_priority_fees
`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_priority_fees payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_priority_fees",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "tool": {
+      "const": "get_priority_fees",
+      "description": "the tool that produced this payload",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "data"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent and open-world traits, so the bar is lower; the description adds genuinely non-structured context: the data is a live "right now" snapshot over a ~150-slot window, and each call costs 0.005 USDC via x402 (USDC on Solana, Base, Polygon, Arbitrum or Arc). The paid/auth requirement is the kind of behavioral detail annotations cannot convey. It stops short of noting any rate limits or freshness guarantees.

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?

Three sentences, front-loaded with the definition of the metric before the audience and the price. Dense but every clause carries information; the parenthetical payment-network list is slightly bulky but justified for an x402 tool.

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

Completeness4/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 structure is already covered. Given no input parameters, a rich output schema, and full annotation coverage, the description supplies everything else a caller needs: what the numbers mean, their units, freshness, and cost. Only the absence of alternative-tool routing keeps it from a 5.

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 input parameters, so the baseline is 4; there is nothing for the description to compensate for. It does add unit semantics (micro-lamports per compute unit) that frame how callers should read the tool's output.

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 priority fees) and then defines the measurement precisely: percentiles from min to max of per-slot minimum fee on the busiest SOL/USDC pools over ~150 slots, in micro-lamports per compute unit, plus a recommended level. An agent can distinguish it from the adjacent get_jito_tips sibling 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?

"For bots that need their transactions to land" gives an implied use context, which is real but thin. It names no alternative (notably get_jito_tips, which is the closest sibling for landing transactions via block-engine tips) and states no when-not condition, so the routing decision is left to inference.

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.