Skip to main content
Glama

My MCP Server

priority-fee-oracle

Live Solana Mainnet priority-fee-oracle ($0.10 USDC via x402 v2 PAYMENT-SIGNATURE header)

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-oracle"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintNo
targetWalletNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does add one genuinely useful fact beyond structured data — the $0.10 USDC cost via an x402 v2 PAYMENT-SIGNATURE header — but says nothing about what the call returns, latency/freshness of the "live" data, or failure modes when payment is missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but that shortness reflects under-specification rather than economy. The one useful detail (payment requirement) is buried in parentheses after a name-like fragment.

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

Completeness1/5

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

With no annotations, no output schema, and two undocumented parameters, the description should explain inputs and expected output shape; it explains neither. Only the payment mechanism is covered, leaving the agent unable to invoke the tool correctly.

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

Parameters1/5

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

Both parameters (mint, targetWallet) have 0% schema description coverage, and the description does not mention them at all. An agent cannot tell whether mint is required for a token-specific fee estimate or whether targetWallet selects a fee-payer account.

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

Purpose2/5

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

"Live Solana Mainnet priority-fee-oracle" essentially restates the tool name and adds only network scope; it never states what the tool actually does (return current priority-fee estimates? per-mint fee recommendations?). There is no verb and no differentiation from siblings such as solana-tps-health-monitor or sol-usdc-spread-scanner.

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

Usage Guidelines1/5

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

The description contains no when-to-use guidance, no prerequisites, and no reference to any alternative tool. An agent has no basis for choosing this over other Solana data tools in the catalog.

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