Scholar Sidekick

Export Citation

exportCitation

Read-onlyIdempotent

Export scholarly identifiers to a bibliography file format ready to write to disk or paste into a reference manager. Use when the user wants a file (.bib, .ris, .nbib, .xml, .rdf, .csv) for Zotero, Mendeley, EndNote, RefWorks, BibTeX/LaTeX, Pandoc, or Excel. Format parameter is required: bib (BibTeX — LaTeX), ris (RIS — most widely supported by reference managers), csl (CSL JSON — Pandoc/Quarto), endnote-xml, endnote-refer, refworks, medline (NBIB — PubMed round-trips, clinical workflows), zotero-rdf, csv (spreadsheet-friendly), or txt (plain-text bibliography rendered with the optional style parameter — txt is the only format that uses style; the others have their own structured shape and ignore it). Accepts the same identifier formats as resolveIdentifier (DOI/PMID/PMCID/ISBN/arXiv/ISSN/ADS/WHO IRIS, prefixes tolerated), single or comma/newline-separated batch — one round trip per call. Returns: { content: string, format: string } where content is the entire bibliography in the requested format as a single string — write it to a file (.bib/.ris/.nbib/etc.) or paste it directly into the target tool. Use formatCitation instead when the user wants in-line citation text (manuscript, slide); use resolveIdentifier when they want raw structured metadata. Read-only and idempotent — safe to retry. Works anonymously against the public Scholar Sidekick API (rate-limited free tier); set SCHOLAR_API_KEY (a free ssk_ key from https://scholar-sidekick.com/account) for higher limits, or RAPIDAPI_KEY for paid RapidAPI tiers. Rate limits follow your tier.

Input Schema

TableJSON Schema

Name	Required	Description
`lang`	No	Locale for formatting (e.g. en-US)
`text`	Yes	One or more identifiers (DOIs, PMIDs, ISBNs, etc.) separated by newlines or commas
`style`	No	Citation style (used only for txt export)
`format`	Yes	Export format

Output Schema

TableJSON Schema

Name	Required	Description	Default
`format`	Yes	The export format that was produced.
`content`	Yes	The entire bibliography in the requested format, as one string.

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already provide readOnlyHint and idempotentHint. The description adds rate limits, API key tiers, batch behavior (one round trip per call), and retry safety—all without contradicting annotations.

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 description is long but packed with useful information, front-loading the main purpose. Every sentence adds value, though it could be slightly more concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (4 params, enum, output schema), the description thoroughly covers usage, return format, API keys, and retry safety. It is complete enough for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant value by explaining each enum value for format (e.g., 'ris' is widely supported), that style only works with txt, and that text accepts same identifier formats as resolveIdentifier.

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?

The description clearly states the tool exports scholarly identifiers to bibliography files with specific formats and use cases. It distinguishes from siblings like formatCitation and resolveIdentifier.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool (file export), when to use formatCitation (in-line text), and when to use resolveIdentifier (raw metadata). Also explains batch usage and format parameter requirements.

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

All Scholar Sidekick tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0

Disambiguation5/5

Each tool targets a distinct function: OA status, retraction status, identifier resolution, citation formatting, citation export, and citation verification. There is no overlap in purpose.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with camelCase (e.g., checkOpenAccess, resolveIdentifier). No mixing of styles.

Tool Count5/5

Six tools is well-scoped for a scholarly citation server. Each tool serves a clear need without being excessive or insufficient.

Completeness4/5

The tool set covers core tasks: lookup, verification, formatting, and export. Missing a search or discovery tool, but that's outside the stated purpose.

Resources

Need Help?