Skip to main content
Glama

YRUZ Network Fees (0.002 USDC)

network_fees
Read-onlyIdempotent

What a transaction costs right now: Solana priority fee levels (low to very high, micro-lamports per compute unit) and the USD cost of a typical transfer and swap, plus Base gas price, base fee and the USD cost of an ERC-20 transfer. Use it to set fees that land without overpaying. Price: 0.002 USDC per call, paid with x402 (USDC on Base or Solana, no account, no API key); invalid input is refused before payment and a failed run is never charged. Without a payment the tool returns the x402 PaymentRequired. How to call it: get_example {"tool":"network_fees"}. Same tool over HTTP: https://yruz.one/api/crypto/fees

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

Input Schema

NameRequiredDescriptionDefault
accountNooptional Solana program or account to estimate for (default: Jupiter router)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description is free to add the materially important context: a 0.002 USDC x402 price, no account or API key needed, invalid input refused before payment, failed runs never charged, and a PaymentRequired response without payment. Those are exactly the behavioral facts an agent needs and cannot get from annotations or schema.

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?

Front-loaded correctly: outputs first, then the usage rationale, then payment mechanics, then the example pointer and HTTP equivalent. It is longer than average but every block carries operational weight; the price is stated in the title and reiterated in prose, a minor redundancy.

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?

With no output schema, the description takes on the burden of describing return values and does so concretely (fee levels low→very high, USD costs for transfer/swap, Base gas and base fee). Payment failure modes and the get_example escape hatch are also covered, leaving nothing essential missing for correct invocation.

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 only one optional parameter and the schema already carries a 100% description ('optional Solana program or account to estimate for, default: Jupiter router'). The description adds nothing about the account parameter — no guidance on when supplying one changes the returned estimates — so it neither helps nor hurts beyond the schema baseline.

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 names the specific resource and enumerates exactly what is returned: Solana priority fee levels in micro-lamports per compute unit, USD cost of a typical transfer and swap, Base gas price and base fee, and USD cost of an ERC-20 transfer. That level of specificity separates it cleanly from neighbors like crypto_price (asset prices) and solana_tx_explain (explaining a past transaction).

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?

It gives one explicit use case — "Use it to set fees that land without overpaying" — which implies the fee-setting context. But there are no stated exclusions or named alternatives for when a caller should prefer crypto_price, solana_token_check, or solana_tx_explain instead, so the routing guidance is implied rather than spelled out.

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.