Skip to main content
Glama

Racketeer Pre-Trade Checks (Solana)

priority fee

priority_fee
Read-onlyIdempotent

What priority fee should my Solana transaction pay right now so it lands? Price $0.005 per call via x402 (USDC on Solana or Base). When payment is needed the tool returns x402 payment instructions instead of data. Not financial advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "priority_fee"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountsNoOptional comma-separated writable accounts (up to 10) (e.g. whirLbMiicVdio4qvUfM5KAg6Ct8VwpYzGff3uctyCc)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, and idempotent, so safety is covered. The description adds substantive behavior beyond that: a $0.005 per-call price, the x402 payment mechanism, and the important failure mode that the tool returns payment instructions instead of data when payment is required. That payment gate is exactly the kind of non-obvious behavior an agent needs before calling.

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?

The core purpose is front-loaded in the first clause, followed by cost and payment-fallback details in a compact form. The closing 'Not financial advice' is low-value boilerplate but short enough not to be a real defect.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should hint at what a fee recommendation looks like (lamports, micro-lamports per CU, priority level), but it only describes the payment-instruction fallback. For a one-parameter read tool this is mostly adequate, yet the return format remains undefined.

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

Parameters3/5

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

There is a single optional parameter and schema description coverage is 100%, so the schema already explains the comma-separated writable accounts. The description adds nothing about how accounts influence the fee estimate (e.g., account contention affecting priority), so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and intent: the priority fee a Solana transaction should pay right now. It is framed as a user question rather than a verb+resource phrase, but the meaning is unambiguous and distinguishable from sibling tools like token_safety or trend_verdict.

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?

The phrase 'right now' implies this is for live, current fee estimation rather than historical analysis, which is useful context. However, there is no explicit when-to-use vs. when-not guidance and no named alternative for related queries, so the agent must infer selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources