Skip to main content
Glama

Scholar Sidekick

by com.scholar-sidekick

Format Citation

formatCitation
Read-onlyIdempotent

Format scholarly identifiers into a finished citation in a specific style. Use when the user wants a paste-ready citation string for a manuscript, slide, message, footnote, or in-line reference. Style defaults to vancouver if unspecified; ask the user before defaulting if any ambiguity exists (e.g. 'Harvard' and 'Chicago' have multiple variants — confirm which one). Supports five hand-tuned builtins (vancouver, ama, apa, ieee, cse) plus any of 10,000+ CSL style IDs (chicago-author-date, harvard-cite-them-right, modern-language-association, nature, bmj, the-lancet, etc.). Alias and dependent-style resolution apply, so 'harvard' resolves to 'harvard-cite-them-right' and the canonical ID is reported back as styleUsed. Output defaults to text; pass output=html for marked-up HTML or output=json for structured CSL items. 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: one of { text, html, items } depending on the output parameter, followed by a metadata block ({formatter: 'builtin' | 'csl', styleUsed, requestId, warnings?}) appended as a second text content item — surface this to the user when they care about reproducibility. Use resolveIdentifier instead when the user wants raw metadata to inspect or transform; use exportCitation when they want a downloadable bibliography file. 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
NameRequiredDescriptionDefault
langNoLocale for formatting (e.g. en-US, en-GB, fr-FR)
textYesOne or more identifiers (DOIs, PMIDs, ISBNs, arXiv IDs, etc.) separated by newlines or commas
styleNoCitation style: vancouver (default), ama, apa, ieee, cse, or any CSL style ID
outputNoOutput format (default: text)
footnoteNoFormat as footnotes instead of bibliography entries

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
htmlNoFormatted citation HTML (when output=html).
langNoLocale used for formatting.
textNoFormatted citation text (when output=text).
itemsNoStructured CSL items (when output=json).
warningsNo
formatterNoWhich engine formatted: 'builtin' or 'csl'.
styleUsedNoCanonical style ID after alias/dependent-style resolution.

TDQS

A4.9/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), adds idempotency detail, API key requirements, rate limits, and return structure including a metadata block.

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?

Fairly long but well-structured with front-loaded purpose. Every sentence adds value, though could be slightly tightened without losing content.

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?

Covers all aspects: usage context, parameter details, output structure, API keys, rate limits, and distinguishes from siblings. Complete given complexity and existing output schema.

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

Parameters5/5

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

Adds significant meaning beyond schema: explains default style, alias resolution, batch processing, output options, and example CSL IDs. Schema coverage is 100% but description greatly enhances understanding.

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?

Describes a specific verb (format) and resource (scholarly identifiers into a finished citation) and clearly distinguishes from siblings like resolveIdentifier and exportCitation.

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 ('paste-ready citation string') and when not to use alternatives, and advises to ask user before defaulting style if ambiguous.

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

All Scholar Sidekick toolsInspect
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