Skip to main content
Glama

Quill Scholar Research Desk

Redeem a transfer for a pass (free)

redeem_transfer_pass
Read-only

FREE. After sending USDC on Base to the address in payment_options, give the transaction hash to get your Quill Research Pass token. Redeeming the same hash again returns the same token.

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

Input Schema

NameRequiredDescriptionDefault
txYes0x-prefixed transaction hash of your USDC transfer on Base

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, and the description adds real context beyond them: the operation is free, it depends on an on-chain USDC payment on Base, and it is idempotent (same hash returns the same token). The idempotency note also reconciles the 'redeem' framing with the read-only annotation, though the apparent tension between 'FREE' and an USDC transfer is left unexplained.

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?

Three short sentences, front-loaded with the cost qualifier and then the prerequisite-then-action sequence. Every sentence carries information; only the opening 'FREE.' is slightly ambiguous on its own.

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?

For a one-parameter tool with no output schema, the description covers what the caller receives (a Pass token) and the idempotent return behavior. It omits how much USDC to transfer, whether confirmations are required before redeeming, and what happens on an unrecognized hash, which are the remaining operational gaps.

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 parameter already documents '0x-prefixed transaction hash of your USDC transfer on Base'. The description restates that meaning rather than adding format, validation, or chain-confirmation details, so the baseline of 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 and resource with its outcome: give a transaction hash to 'get your Quill Research Pass token'. It also names the sibling payment_options as the prerequisite source of the address, so the agent can place the tool in the workflow without opening a schema.

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 precondition for use: send USDC on Base to the address in payment_options first, then call this with the hash. It does not state what to do when the transfer is on another chain, pending, or invalid, so exclusions are implied rather than explicit.

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