Skip to main content
Glama
Sign In
pandadad0214

Panda Federation Tools

by pandadad0214
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Citation Generator API: DOI to APA, MLA, Chicago & BibTeX

citation_formatter
Read-only

Converts DOIs, ISBNs, PMIDs, arXiv IDs, titles or messy references into APA, MLA, Chicago, Harvard, IEEE, Vancouver, BibTeX and RIS citations checked against Crossref.

Instructions

Use this to turn DOIs, ISBNs, PMIDs, arXiv IDs, titles or messy references into citations. Input: a reference list or pasted .bib/.ris text. Output: APA 7, MLA 9, Chicago, Harvard, IEEE, Vancouver, BibTeX and RIS per reference, checked against Crossref.

Runs the Apify Actor pandadad0214/citation-formatter (https://apify.com/pandadad0214/citation-formatter) on your own Apify account. Price: $0.003 per citation formatted. Runs that find nothing are not charged per result. Spending is capped per call by run_max_charge_usd.

Input Schema

NameRequiredDescriptionDefault
textNoPaste a reference list or file contents. Optional. Paste a whole bibliography (numbered, one per line, or blank-line separated), or the contents of a .bib (BibTeX) or .ris file. BibTeX/RIS entries are converted directly without a lookup.
stylesNoCitation styles. Styles to output. All six are included in the price, so pick as many as you like.
includeRisNoRIS export. Add an RIS entry per reference and a combined .ris file (Zotero, Mendeley, EndNote, Rayyan). Default: on.
referencesNoReferences (one per line). DOIs, DOI links, ISBNs, arXiv IDs, PMIDs ("PMID: 123"), paper titles, or messy reference strings in any style. Each one is looked up and formatted.
contactEmailNoContact email for Crossref (optional). Optional. Sent to Crossref and NCBI as the contact so requests use their faster 'polite' pools. Never shared elsewhere.
includeBibtexNoBibTeX export. Add a BibTeX entry per reference and a combined .bib file (LaTeX, Overleaf, JabRef). Default: on.
maxReferencesNoMax references per run. Safety cap. Only formatted citations are billed. Whole number, 1 to 20,000 references; default 1,000.
minMatchScoreNoMinimum match score for text lookups (50-100). How closely a search result must match a free-text reference (title, authors, year) to be used. DOIs and ISBNs are exact lookups and are not affected. Whole number, 50 to 100; default 80.
run_max_itemsNoOptional. Most results to return from this call (default from PANDA_MAX_ITEMS, 50). Also limits how many results the Actor produces and charges for, unless you set its own max field.
fixAllCapsTitlesNoFix ALL-CAPS titles. Some registry records store titles in capitals. Convert them to sentence case. Default: on.
run_timeout_secsNoOptional. Seconds to wait for results (default from PANDA_TIMEOUT_SECS, 120; max 300).
run_max_charge_usdNoOptional. Hard spending cap for this call in USD (default from PANDA_MAX_CHARGE_USD, 0.50).
sentenceCaseTitlesNoSentence-case article and book titles. APA, Harvard, IEEE and Vancouver use sentence case ("Deep residual learning for image recognition"). Registries often store Title Case, so we convert it; acronyms like CVPR, mRNA and COVID-19 are kept. MLA and Chicago re-capitalise automatically. Check proper nouns (names, places) in converted titles. Default: on.
listUnresolvedInFilesNoList unresolved references in the bibliography files. Append references we could not find to the end of each bibliography file, marked [UNRESOLVED - check manually], so nothing silently disappears. They are never charged. Default: on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnly, openWorld, non-idempotent, non-destructive) it discloses the execution model, per-citation pricing of $0.003, that unresolved references are not charged, and that spending is hard-capped per call by run_max_charge_usd. This is exactly the billing and side-effect context an agent cannot get from structured fields.

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?

Front-loaded with the capability and input/output contract before the operational boilerplate, and each sentence carries information. There is mild redundancy from the 'Input:'/'Output:' labels restating what the schema already enumerates, but nothing is wasted at length.

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 14-parameter tool with no output schema, the description covers the return shape (per-reference APA/MLA/Chicago/Harvard/IEEE/Vancouver plus BibTeX and RIS), resolution source (Crossref), billing, and caps. Remaining gaps are minor, such as the structure of run results beyond the bibliography files.

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%, so every one of the 14 parameters is already documented in the schema, including enum and range details. The description adds only framing (which identifier types are accepted, that all six styles are included in the price) rather than new per-parameter semantics, 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 specific verb and resource ('turn DOIs, ISBNs, PMIDs, arXiv IDs, titles or messy references into citations'), enumerates both accepted input forms and the eight output formats, and is clearly distinguishable from siblings such as reference_checker or literature_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: paste a bibliography or .bib/.ris contents, or pass individual references, and it explains that BibTeX/RIS entries are converted without a lookup while other identifiers are resolved. It never explicitly excludes cases or names a sibling alternative (e.g., when to prefer reference_checker), 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.

Deploy Server

Other Tools