Skip to main content
Glama
Sign In

Tlacuilo

by io.github.mastercobeos
OverviewDiscussionsAdmin

papers_cite

papers_cite
Read-only

Formatted citation for any DOI registered with Crossref or DataCite (journal articles, books, arXiv preprints, datasets): BibTeX entry plus a formatted reference in APA, MLA, Chicago author-date, IEEE, Harvard, Nature or AMA style. Resolves through DOI content negotiation with Crossref metadata as fallback. Price: $0.002 USDC per call (x402).

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": {
      "doi": "<doi>"
    },
    "name": "papers_cite"
  }
}

Input Schema

NameRequiredDescriptionDefault
doiYesDOI, with or without the https://doi.org/ prefix
styleNoapa (default), mla, chicago, ieee, harvard, nature or ama

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?

Beyond the readOnlyHint annotation, the description discloses the resolution mechanism (DOI content negotiation with Crossref metadata fallback) and a paid-call constraint ($0.002 USDC per call via x402), which is critical pre-invocation context an agent would not get from annotations or schema. It omits error behavior for unresolvable DOIs.

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 tight sentences, front-loaded with the core capability, followed by resolution behavior and price. The style enumeration duplicates the schema slightly, but nothing is wasted or buried.

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 usefully tells the agent what comes back (BibTeX entry plus a formatted reference). It covers cost and resolution path; the only missing piece is failure handling for DOIs not registered with either agency.

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 doi and style are already documented in the schema. The description restates the style list and DOI scope but adds no format, default, or validation detail beyond what the schema provides, 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?

States a concrete verb+resource: produce a formatted citation (BibTeX plus a styled reference) for a DOI. Names the supported identifier sources (Crossref/DataCite) and covered materials (articles, books, arXiv, datasets), which clearly separates it from the search-oriented sibling papers_search.

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 clear context for use: the caller supplies a DOI registered with Crossref or DataCite and picks a citation style. It doesn't explicitly state exclusions (e.g., what to do for non-registered DOIs or when to prefer papers_search to find a DOI first), so it stops short of full when/when-not guidance.

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

All Tlacuilo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources