Skip to main content
Glama
Sign In
gasrescue

gasrescue MCP server

Official
by gasrescue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get what the wallet must sign

get_signing_request
Read-onlyIdempotent

Retrieve the exact payload a wallet must sign for a send or swap quote, then pass it to submit_signatures. Fails if the quote expired, so request a new quote.

Instructions

Returns what the sender's wallet has to sign for a quote from quote_send or quote_swap. kind "evm-typed-data": sign every steps[].typedData with eth_signTypedData_v4, in order (one authorization, or for permit tokens a permit plus the order itself); binding is the order the authorization commits to, so recipient, fee and minimum can be checked first. kind "tron-transactions": sign every steps[].transaction (first the fee, then the transfer). kind "solana-transaction" or "solana-versioned-transaction": sign the base64 transaction. Read-only. Pass the result to submit_signatures. Fails when the quote expired; then request a new quote.

Input Schema

NameRequiredDescriptionDefault
transferIdYesThe id gasrescue returned as transfer.id from quote_send or quote_swap: 24 lowercase hex characters, e.g. "b39f46001a5680455091152d". Not a transaction hash and not an id of another service.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.6
    • changedInput schema / properties / transferId / description
      Previous value: -"The transfer id returned by quote_send or quote_swap (24 hex characters)."New value: +"The id gasrescue returned as transfer.id from quote_send or quote_swap: 24 lowercase hex characters, e.g. \"b39f46001a5680455091152d\". Not a transaction hash and not an id of another service."
  2. Changed2 schema fields changedv0.1.5
    • changedInput schema / properties / transferId / description
      Previous value: -"The transfer id from a quote."New value: +"The transfer id returned by quote_send or quote_swap (24 hex characters)."
    • addedInput schema / properties / transferId / pattern
      Added value: +"^[0-9a-f]{24}$"
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds substantial context on top: the sign-ordering rules per kind, the semantics of the binding field, what should be verified (recipient, fee, minimum) before signing, and the expiry failure mode with the recommended recovery. This is behavior an agent cannot get from the annotations.

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 return statement, then organized by kind in a scannable sequence, ending with the failure mode. It is dense and slightly run-on in the evm-typed-data clause, but nearly every sentence carries signing instructions the agent needs.

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?

There is no output schema, so the description carries the burden of explaining return shape, and it does so thoroughly by enumerating each kind and its corresponding step fields. Combined with the sequencing and expiry behavior, an agent has everything needed to call it and act on the result.

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 single transferId parameter is already fully described in the schema (pattern, format, provenance from quote tools, explicit non-transaction-hash warning). The description adds nothing about the parameter itself, so the baseline 3 applies.

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 (returns the signing payload for a quote) and immediately names the upstream siblings that produce the quote (quote_send, quote_swap) and the downstream consumer (submit_signatures). The per-kind enumeration of what is returned makes it unmistakable versus get_transfer or quote_* tools.

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?

Explicitly routes the agent: call after quote_send/quote_swap, then pass the result to submit_signatures, and if the quote expired, request a new quote instead. It lacks an explicit when-not/exclusion statement, but the sequencing is clear enough that no alternative tool is plausibly confused with this one.

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

Deploy Server

Other Tools