Skip to main content
Glama

Credit top-up message

agentgas_credit_message
Read-only

Free. Returns the exact EIP-191 message to sign with the payer wallet to spend prepaid credit on a top-up (no x402 payment). Then POST /v1/gas {credit:{message,signature}}. Credit: start with a 0.09 USDC pack (fits the $0.10 x402 cap, 0.099 credit) or 5/10/20 USDC packs, all with +10% bonus, at /v1/credit?pack=0.09.

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": {
      "payer": "<payer>",
      "chain": "<chain>"
    },
    "name": "agentgas_credit_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
usdNo
chainYesDestination chain for the native gas
payerYes
amountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only and open-world behavior, while the description adds that the call is free, involves no x402 payment, returns an exact signing message, and feeds a specific next step. It does not cover auth or rate limits, but it adds meaningful behavior beyond 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-loads the key points: free, exact EIP-191 message, no x402 payment, then the follow-up POST and credit pack details. It is somewhat dense with endpoint and pack details, but there is little wasted wording.

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?

Explains what is returned and what to do next, which helps because there is no output schema, but for a five-parameter tool with low schema coverage it leaves important input semantics unclear. It is adequate but incomplete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20%, so the description should compensate, but it does not explain payer format, chain enum meaning, or how to, usd, and amount affect the message. It only implicitly references the payer wallet and gives pack pricing context, leaving most parameters undocumented.

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 specifically that it returns the exact EIP-191 message to sign with the payer wallet to spend prepaid credit on a top-up, explicitly with no x402 payment. This is a clear verb/resource purpose that distinguishes it from an x402 payment flow.

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 a clear workflow: call this to get the message, then POST /v1/gas with credit message and signature. It also provides credit pack guidance, though it does not explicitly name alternatives or state when not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources