Jito bundle tip-floor snapshot + rolling history (p50/p95/p99/EMA). Optional ?fresh=true bypasses the ~60s cache for a live snapshot.
| Name | Required | Description | Default |
|---|---|---|---|
| fresh | No | If 'true', bypass the ~60s cache and fetch a live tip-floor snapshot (otherwise a cached snapshot is served). |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so description carries the burden. It discloses cache TTL and the fresh bypass, but does not confirm read-only behavior or possible failure modes.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no redundant wording; key details are front-loaded and scannable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Mentions output metrics (p50/p95/p99/EMA) and cache semantics, though the exact return shape is not specified. Adequate for a simple data lookup tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The sole parameter 'fresh' is well-explained in the schema, and the description adds the 'otherwise cached' contrast for clarity.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clear resource (Jito bundle tip floor) and action (snapshot + rolling history) with specific metrics. Distinguishes from sibling tools like priority_fee, though not explicitly by name.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explains cache behavior and the fresh=true bypass, but does not explicitly state when to prefer this tool over related alternatives such as priority_fee.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.