Skip to main content
Glama

AgentFeed

by io.github.seekdaseek
OverviewDiscussionsAdmin

Jito tip floor

get_jito_tips
Read-onlyIdempotent

Jito tips: bundle tip floor percentiles from p25 to p99 in SOL — what landed bundles are actually paying — with an EMA p50 and a landing recommendation. Costs 0.005 USDC per call (x402, USDC on Solana or Base).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesthe get_jito_tips payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_jito_tips
toolYesthe tool that produced this payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": {},
+      "description": "the get_jito_tips payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_jito_tips",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "tool": {
+      "const": "get_jito_tips",
+      "description": "the tool that produced this payload",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "data"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare it read-only, open-world, idempotent, and non-destructive; the description adds valuable operational context: a hard cost of 0.005 USDC per call, payment via x402, and accepted USDC networks (Solana or Base). It also clarifies the payload shape (percentiles plus EMA and recommendation).

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 load-bearing. The data content is front-loaded, and the cost/payment details are tucked into a single compact second sentence. There is no filler or repetition of the annotations.

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 no-input, read-only tool with an output schema, the description covers what is returned, in what unit (SOL), and the key operational constraint (cost and payment rails). No other parameter, prerequisite, or return-value detail is necessary for an agent to invoke it 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 has zero parameters, so the baseline is 4. The description adds no parameter semantics, but none are needed; instead it clarifies the data scope and units an agent can expect without any 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?

The description states exactly what the tool returns: Jito bundle tip floor percentiles p25–p99 in SOL, an EMA p50, and a landing recommendation. This goes well beyond the title 'Jito tip floor' and distinguishes it from the many other market-data getters in the sibling list.

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

Usage Guidelines2/5

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

There is no explicit guidance about when to call this tool versus alternatives such as get_priority_fees or pricing. The phrase 'what landed bundles are actually paying' implies a use case, but the description never states the intended context or conditions that should select this tool.

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

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