hyperd-mcp

Official

Overview Schema Source Related Servers Discussions Admin

hyperd.gas.estimate

Estimate gas fees with base fee and tip percentiles for fast, standard, or slow inclusion on multiple chains. Pay $0.005 USDC per request.

Instructions

Get current gas price + base fee + tip percentiles for fast/standard/slow inclusion. Costs $0.005 in USDC.

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": "hyperd.gas.estimate"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	No	Chain. Default 'base'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 11, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It discloses a cost of $0.005 USDC, but does not clarify if the operation is read-only or any other side effects.

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?

Two concise sentences with key action and cost, no wasted words, front-loaded with primary function.

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?

Given low complexity (1 optional parameter, no output schema), the description adequately covers what is returned and the cost, though it could briefly mention return format or units.

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?

Schema coverage is 100% and the parameter 'chain' is already described in the schema as 'Chain. Default ''base'''. The description adds no new semantic information beyond that.

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 verb 'Get' and the resource 'current gas price + base fee + tip percentiles for fast/standard/slow inclusion', distinguishing it from sibling tools like balance.get or dex.quote.

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?

The description implies use for gas estimates but provides no explicit guidance on when to use or not, nor any alternatives.

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