Skip to main content
Glama

Solana congestion

gas_tracker
Read-only

Solana network congestion monitor. Returns current fee percentiles, congestion level (LOW/MODERATE/HIGH/VERY_HIGH), and a plain-English recommendation. Costs $0.0005 USDC per call.

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": "gas_tracker"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the paid nature of the call ('Costs $0.0005 USDC per call') and the exact shape of the return payload including the four-value congestion enum. It does not state freshness/staleness of the data or whether the recommendation is deterministic, which are the remaining behavioral gaps.

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?

Three short sentences: identity first, return values second, cost last. Nothing is redundant and the most decision-relevant facts are front-loaded.

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?

With no parameters and no output schema, the description carries the burden of describing the response, which it does via the enumerated return values and the congestion enum. The only shortfall is the absence of guidance versus the related fee/gas siblings (priority_fee, l2_gas_intelligence).

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies no inputs are required.

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 names a specific resource and scope ('Solana network congestion monitor') and enumerates the outputs (fee percentiles, LOW/MODERATE/HIGH/VERY_HIGH congestion level, plain-English recommendation). It implicitly separates itself from the L2-focused sibling l2_gas_intelligence by specifying Solana, but never names an alternative explicitly.

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?

Usage is only implied — an agent can infer this is for checking Solana fees before submitting a transaction. There is no explicit statement of when to prefer this over priority_fee or l2_gas_intelligence, and no prerequisites or exclusions are given.

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