Skip to main content
Glama
gasrescue MCP server

gasrescue MCP server

Official

Supported chains, tokens and fees

gasrescue_info
Read-onlyIdempotent

Call this first to get the supported chains, stablecoins and gas coins, plus fees and limits the other tools need. Read-only and takes no input.

Instructions

Lists what gasrescue supports: the chains, the stablecoins on each, which chains can swap into their gas coin, the fees and the limits. Use gasrescue when a wallet holds USDC, USDT or USDG but no ETH, POL, AVAX, BNB, SOL, TRX or HYPE for the network fee ("insufficient funds for gas"). Call this first to get the chain keys and token symbols the other tools expect. Read-only, takes no input. Returns network, fees (service percent, minimum, maximum), limits (USD per transfer, transfers per wallet per day, quote validity) and the chains with their tokens and gas coin. gasDrop: true marks a chain without a gasrescue contract (BNB Chain): there gasrescue sends the wallet a little gas and the wallet sends two plain transfers itself.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds real behavioral value beyond that: no input required, the exact shape of what comes back (network, fees, limits, tokens per chain, quote validity), and the non-obvious gasDrop case where BNB Chain has no gasrescue contract and the wallet must send two plain transfers itself. Only gap is error/rate-limit behavior, which is minor here.

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 with the supported-assets summary, then usage conditions, then ordering guidance, then return shape. Dense but every clause carries information; the gasDrop explanation is long but covers a genuinely surprising execution path, so it earns its place.

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 the return payload and does so field-by-field (fees percent/min/max, USD per transfer, transfers per wallet per day, quote validity, gasDrop flag). Combined with zero-param simplicity and covered annotations, nothing needed to invoke and interpret this tool is missing.

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?

Zero parameters, so the schema carries everything and the baseline is 4. The description correctly states 'takes no input', which prevents an agent from inventing arguments.

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?

States a specific verb and resource set — chains, stablecoins per chain, swap-capable gas coins, fees and limits — and positions itself relative to siblings by saying the chain keys and token symbols it returns are what the other tools expect. An agent can immediately tell this is the discovery/config tool rather than a quote or execution tool.

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

Usage Guidelines5/5

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

Gives an explicit trigger scenario (wallet holds USDC/USDT/USDG but no native gas coin, error 'insufficient funds for gas') and an explicit ordering rule ('call this first') before quote_send/quote_swap/get_transfer etc. The when-not case is implicit but the alternative is clearly the rest of the sibling set.

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