Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_fee_estimate

Read-only

Estimate the total fee in mojos required for a Chia transaction to be included within specified target times, using transaction cost or a spend bundle.

Instructions

Estimate the fee required for a transaction to be included within target times. Provide target times in seconds (e.g., [60, 300, 600] for 1min, 5min, 10min). Returns the total estimated fee in mojos for the given cost at each target time. current_fee_rate is mojos per CLVM cost unit. If neither cost nor spend_bundle is provided, cost defaults to 5,000,000 (the node's default sample bucket). A standard two-input two-output XCH send costs approximately 17,000,000 CLVM cost units (this is the standalone single-bundle cost; in-block cost is lower due to generator compression, but fee estimation uses the standalone figure); use that for realistic fee estimation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target_times": "<target_times>"
    },
    "name": "get_fee_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
costNoOptional transaction cost in CLVM cost units (alternative to providing spend_bundle). Defaults to 5,000,000 (fee-estimation sample bucket) if neither cost nor spend_bundle is provided.
spend_bundleNoOptional spend bundle to estimate fees for (provides accurate cost calculation)
target_timesYesArray of target times in seconds (e.g., [60, 300, 600])

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds the default cost bucket (5,000,000), the return shape (total fee in mojos per target time), unit semantics, and a non-obvious caveat that fee estimation uses the standalone single-bundle cost rather than in-block cost. That is substantial context beyond structured fields.

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?

It is front-loaded with the purpose, then units, then defaults, then the practical cost figure. The final sentence is a long parenthetical that packs several caveats together, but nearly every clause carries information an agent would otherwise get wrong.

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 output schema, the description correctly describes the return value (total estimated fee in mojos at each target time). One residual gap: it references current_fee_rate, which is not among the three input parameters, which may briefly confuse an agent about what to supply.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes further by giving the realistic 17,000,000 CLVM figure for a standard two-in two-out XCH send, which appears nowhere in the schema and is the key number an agent needs for a sensible estimate.

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 opens with a specific verb and resource: estimating the fee required for a transaction to land within target times. There is no sibling tool that estimates fees, so the scope is unambiguous and an agent can select it immediately.

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

Usage Guidelines4/5

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

It explains the required input (target times in seconds, with a concrete example array) and the fallback rule when neither cost nor spend_bundle is supplied. It does not spell out when to prefer cost over spend_bundle beyond 'accurate cost calculation', leaving that choice partly to inference.

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