Skip to main content
Glama

Quill Scholar Research Desk

How to pay (free)

payment_options
Read-only

FREE. Prices, the plain-USDC-transfer research pass (1 / 5 / 15 USDC on Base for 24 h / 7 days / 30 days), the x402 per-call alternative, and the status of the pass you are using (if any).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "payment_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
passNoOptional Quill Research Pass token (qp1...). Better: set it once as the MCP header Authorization: Bearer <token>.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 with a safe read. It adds value beyond the annotation by stating the call itself is FREE, spelling out the pricing tiers and the x402 alternative, and disclosing that the tool also reports the status of the pass in use — behavior the annotation alone would not reveal.

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?

A single sentence with 'FREE.' front-loaded so the most decision-relevant fact lands first. The parenthetical tier list is dense but each clause (prices, pass tiers, x402 alternative, current status) corresponds to distinct returned information, so little is wasted.

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 read-only informational tool with no output schema, the description covers what the agent needs: that it is free to call, what pricing/pass options exist, that an alternative x402 path exists, and that it reflects the caller's current pass status. Only the exact response shape remains unstated, which is acceptable here.

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 description coverage is 100% and the schema already explains the optional qp1... token and the Authorization header recommendation. The phrase 'the status of the pass you are using (if any)' reiterates what the parameter controls but adds no format or precedence detail beyond the schema, so 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?

The description names the concrete subject matter: prices, the USDC-transfer research pass with specific tiers (1/5/15 USDC on Base for 24h/7d/30d), the x402 per-call alternative, and the caller's current pass status. That is specific enough to separate it from redeem_transfer_pass, though the verb ('returns'/'describes') is only implied.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer this is the tool to consult for pricing and payment mechanics. There is no explicit 'use this when...' nor a pointer to redeem_transfer_pass for actually obtaining a pass, so the choice between reading options and acting on them is left to inference.

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