Skip to main content
Glama

Quill Scholar Research Desk

Citation formatter

cite
Read-only

A DOI, arXiv id/URL or paper title -> the verified record plus BibTeX, RIS, APA 7, MLA 9, Chicago, IEEE, Harvard and Vancouver citations and in-text forms; for arXiv preprints also the peer-reviewed version if one exists. Needs a Quill Research Pass (1 USDC = 24 h, 5 USDC = 7 days, 15 USDC = 30 days by plain USDC transfer on Base; see payment_options), or pay per call over HTTP x402 ($0.01) at /v1/cite.

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": {
      "id": "<id>"
    },
    "name": "cite"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDOI (10.xxxx/...), doi.org URL, arXiv id (2005.11401) or arxiv.org URL, or a paper title. Omit for a demo.
passNoOptional Quill Research Pass token (qp1...). Better: set it once as the MCP header Authorization: Bearer <token>.
styleNoOne style only (default all).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the read-only and open-world nature, and the description adds genuinely useful behavior beyond them: the paid access model (Research Pass durations and pricing, or $0.01 per-call x402 over HTTP) and the fact that arXiv preprints may resolve to a peer-reviewed version. It doesn't explain failure behavior for unresolvable IDs or whether results are cached, keeping it below 5.

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?

The input->output shape is front-loaded and the pricing tail is compactly stated in a parenthetical. The arrow notation and dense pricing clause are terse but readable; nothing is superfluous, though the sentence is long enough to require re-reading.

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?

With no output schema, the description correctly describes the return payload (verified record plus BibTeX, RIS, APA 7, MLA 9, Chicago, IEEE, Harvard, Vancouver and in-text forms) and explains access/payment prerequisites. It omits error handling and rate/expiry behavior for pass tokens, which keeps it from being fully complete.

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 the baseline is 3; the description largely restates the accepted id formats already documented in the schema rather than adding syntax or edge-case meaning. It does surface an interesting nuance (an omitted id yields a demo), though that slightly conflicts with id being marked required in the schema.

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?

Uses an explicit input->output form: given a DOI, arXiv id/URL or paper title it returns 'the verified record plus' a named list of citation styles and in-text forms, plus peer-reviewed versions for arXiv preprints. The verb and resource are unambiguous, and an agent can tell this is a citation-producing tool rather than a search or reference-checking tool.

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?

The description makes clear when it applies (any DOI/arXiv/title lookup for citation output) and routes the agent to payment_options for pass pricing details. It lacks explicit when-not guidance or comparison against siblings like check_references or search_papers, so it falls short of 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