MIDL MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

midl_estimate_gas

Read-only

Estimate the gas required to execute an EVM transaction on the MIDL blockchain by providing the recipient address and optional value or calldata.

Instructions

Estimate gas required for an EVM transaction before sending.

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": {
      "to": "<to>"
    },
    "name": "midl_estimate_gas"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Target contract or recipient address
`value`	No	Amount of BTC to send (e.g., "0.1")
`data`	No	Transaction calldata (hex)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 25, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description confirms a read-only estimation behavior but adds no additional context about return values or edge cases. It is adequate but does not enrich beyond annotations.

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?

The description is a single, concise sentence with no extraneous words. It is front-loaded with the core purpose.

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?

The description is brief and covers the basic purpose, but omits important context such as the return format (e.g., gas in wei, hex). Without an output schema, the description should provide more completeness for an agent to interpret results.

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?

All three parameters have descriptions in the schema (100% coverage), so the description does not need to add semantic information. It adds nothing beyond the schema, meeting the 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 clearly states the tool's function: estimating gas for an EVM transaction. It uses a specific verb ('Estimate') and resource ('gas required for an EVM transaction'), and no sibling tool overlaps with this purpose.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus other tools, nor are any prerequisites or exclusions mentioned. The description simply states what it does without contextual advice.

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