Skip to main content
Glama

Claim your credits key for a transfer (free)

credits_claim
Idempotent

FREE. Step 2: give the quote id and the Base transaction hash of your USDC transfer; the server reads the receipt and returns your key. Claiming the same quote again returns the same key.

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": {
      "quote": "<quote>",
      "tx": "<tx>"
    },
    "name": "credits_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
txYes0x-prefixed transaction hash of your USDC transfer on Base
quoteYesQuote id from credits_quote (q_ + 32 hex)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (which already declare idempotency and non-destructiveness), the description discloses the key mechanism: the server reads the on-chain receipt to verify the transfer before issuing the key, and repeat claims yield the same key. That adds real behavioral context about verification rather than mere repetition. It does not cover failure modes (e.g. unconfirmed or mismatched tx) or whether the quote becomes consumed.

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 tight sentences with zero waste; the cost signal ('FREE') and the step positioning are front-loaded before the mechanics, and the idempotency note sits last where it belongs.

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?

For a two-parameter, annotated tool with no output schema, the description covers what is required, what is returned (a key), and repeat-call behavior, which is close to complete. It leaves out the prerequisite that a quote and a completed transfer must already exist, and what happens when the receipt check fails.

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 both parameters are already fully documented in the schema, and the description largely restates them (quote id plus Base tx hash). The only added semantics is that the server reads the receipt from that hash, implying the tx must be verifiable on-chain. That is a marginal lift, so 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?

The description states a specific action and its inputs ('give the quote id and the Base transaction hash of your USDC transfer') and its result ('returns your key'), and the 'Step 2' marker clearly positions it relative to the sibling credits_quote without needing to name it. An agent can tell exactly what this tool does and what it produces.

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?

Phrasing it as 'Step 2' implies the prerequisite sequence: get a quote first, then transfer USDC, then claim here. It also gives re-use guidance ('Claiming the same quote again returns the same key'), which tells the agent repeated calls are safe. It stops short of explicit when-not-to-use or naming alternatives, so it is not a 5.

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