Skip to main content
Glama
@gblin-protocol/mcp-server

@gblin-protocol/mcp-server

prepare_gblin_payment

Read-only

Prepare a gasless GBLIN payment without ETH: get the EIP-712 authorization to sign, calldata, and x402 payload, plus optional relay fee.

Instructions

Builds a gasless GBLIN payment. The vault's share token implements EIP-3009, so the holder signs an authorization and anybody can carry it on chain: the payer needs no ETH. Returns the EIP-712 message to sign (its domain is read from the token, not assumed), the calldata that carries the signed authorization, and the x402 'exact' payload for paying an HTTP endpoint in GBLIN. Method 'receive' lets only the named recipient submit the authorization, so nobody can front-run the transfer; method 'transfer' suits an x402 facilitator, which submits on the seller's behalf. With relay: true it also returns a second authorization that pays a relayer's fee in GBLIN. No private key is requested, held or transmitted: the signature is produced by the caller's own wallet.

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

Input Schema

NameRequiredDescriptionDefault
toYesThe recipient's address.
fromYesThe payer's address: the wallet that will sign.
relayNotrue when nobody else will carry the payment on chain: also prepares a second authorization that pays GBLIN's relay fee in GBLIN at the live NAV. Forces method 'transfer'.
methodNo'receive' (default) can be submitted only by the recipient; 'transfer' by anyone.
amount_usdNoAmount in USD, converted at the live NAV. Give this or amount_gblin.
amount_gblinNoAmount in GBLIN shares, e.g. '0.25'. Give this or amount_usd.
valid_for_secondsNoHow long the authorization stays valid. Default 600, maximum 86400.

Output Schema

NameRequiredDescriptionDefault
relayNoWith relay: true, the fee authorization to sign and where to send both.
amountNo
digestYesThe EIP-712 digest of typed_data.
methodYes
submitNo
warningsNo
next_stepsNo
typed_dataYesThe EIP-712 message to sign with eth_signTypedData_v4.
x402_payloadYesThe x402 exact-scheme payment payload, with the signature left to fill.
authorizationYesfrom, to, value, validAfter, validBefore, nonce.
payer_balanceNo
x402_accepts_for_sellersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.4
    • changedInput schema / properties / relay / description
      Previous value: -"true when nobody else will carry the payment on chain: also prepares the relay fee authorization, paid in GBLIN at the live NAV, for relay_gblin_payment. Forces method 'transfer'."New value: +"true when nobody else will carry the payment on chain: also prepares a second authorization that pays GBLIN's relay fee in GBLIN at the live NAV. Forces method 'transfer'."
  2. Addedv1.1.5

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and the description is consistent: the tool only builds and returns messages, never submits or holds keys ('No private key is requested, held or transmitted'). It adds substantive context beyond annotations — EIP-3009/EIP-712 mechanics, domain read from the token rather than assumed, and relay forcing method 'transfer' — but does not discuss validity/expiry consequences or failure modes.

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 what it produces and why it matters, and each sentence carries new information (gaslessness, method choice, relay mode, key safety). It is dense and slightly long, but no sentence is filler.

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?

For a multi-artifact preparation tool with an output schema and full annotation coverage, the description covers inputs, modes, signing flow, and the no-key custody guarantee. Nothing essential to invoking it correctly is missing.

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%, so all seven parameters are already documented in the schema. The description reinforces method/relay semantics and the front-running rationale, but adds little that the schema does not already state (live NAV conversion, default 600s, forced 'transfer'), so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Builds a gasless GBLIN payment') and immediately enumerates the three artifacts returned (EIP-712 message, calldata, x402 payload). It clarifies its role versus a submitting tool through the relay/method discussion, though it never names the actual siblings relay_gblin_payment or verify_gblin_authorization.

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?

Gives explicit selection criteria among its own modes: 'receive' when only the recipient should submit (front-running protection), 'transfer' for an x402 facilitator, and 'relay: true' when nobody else will carry it on chain. It lacks routing guidance against the sibling submit/verify tools, so 4 rather than 5.

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