Skip to main content
Glama

Scholar Sidekick

by com.scholar-sidekick
OverviewDiscussionsAdmin

Audit Bibliography

auditBibliography
Read-onlyIdempotent

Verify a WHOLE bibliography in one call — the batch counterpart to verifyCitation. Each entry runs the same fabrication check (real, resolvable identifier paired with a title that does NOT match the resolved paper; Topaz et al., Lancet 2026) plus a retraction lookup, and the tool returns a per-entry verdict table and a corpus summary. Use when the user pastes a reference list, a .bib / .ris file, or asks to 'check all these citations at once' / 'audit my bibliography' / 'which of these references are fake or retracted'. Input: EITHER bibliography (raw BibTeX / RIS / CSL-JSON text — format auto-detected) OR claims (an array of pre-parsed {title + identifier} objects), not both. Capped at 25 entries per call; excess is dropped and reported via truncated. checks defaults to ['retraction'] (pass [] to skip); screenWithLlm opt-in per entry (same auth gating as verifyCitation). Returns: { format, entries: [{ index, sourceKey?, status: 'ok'|'error', verdict: 'matched' | 'mismatch' | 'not_found' | 'ambiguous', confidence, matched, mismatches, retraction: { checked, doi, isRetracted, hasCorrections, hasConcern, notices } | null, provenance }], parseErrors: [{ index, error, message }], truncated, summary: { total, matched, mismatch, ambiguous, not_found, errored, retracted } }. Reading the result: index is 1-BASED (entry 1 is the first reference) — do not add 1 again when reporting it. sourceKey is the entry's own key in the source file (BibTeX cite key, RIS ID, CSL-JSON id) and is the reliable way to point a user at the offending reference; it is absent on the claims[] path. entries and parseErrors share one index space, so a given input position appears in exactly one of them — report parseErrors as UNCHECKED, never as clean. summary.total counts verifiable entries only, excluding parseErrors and anything past the cap; summary.retracted is a separate axis from the verdict counts (an entry can be both matched and retracted), so never sum those fields. A non-zero truncated means the audit is incomplete — split the bibliography and call again. Per-entry leniency: one entry that fails to resolve becomes status:'error' without failing the batch. This audits citation IDENTITY (does each identifier resolve to the claimed work, and is it retracted) — it does NOT check whether a source supports the claim it is cited for. Read-only and idempotent. Works anonymously for the non-LLM path; SCHOLAR_API_KEY (a free ssk key from https://scholar-sidekick.com/account) or a paid RapidAPI tier raises rate limits and enables the optional LLM screen.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
checksNoPer-entry enrichment checks. Defaults to ['retraction'] (flags retracted / corrected / expression-of-concern works via Crossref + Retraction Watch, keyed on each resolved DOI). Pass [] to skip the retraction lookup.
claimsNoPre-parsed citations to audit — an alternative to `bibliography` for agents that already hold structured references. Each needs a `title` plus whatever identifiers the citation carries.
formatNoOverride format auto-detection for `bibliography`.
bibliographyNoRaw bibliography text to parse and audit — BibTeX, RIS, or CSL-JSON. Provide EITHER this or `claims`, not both. Format is auto-detected from the content; override with `format`. Capped at 25 entries per call (excess is dropped and reported via `truncated`).
screenWithLlmNoOpt-in Stage 3 LLM screen applied per entry (same gating as verifyCitation: authenticated first-party key or paid RapidAPI tier). Default false.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoDetected input format ('bibtex' | 'ris' | 'csl-json'), or null for the claims[] path.
entriesNoOne result per verifiable entry: { index, sourceKey?, status: 'ok'|'error', verdict, confidence, matched, mismatches, retraction, _provenance }. `index` is 1-BASED and counts position in the submitted input, so entry 1 is the first reference — do not add 1 again when you report it to a user. `sourceKey` is the entry's own key in the source file (BibTeX cite key, RIS `ID`, or CSL-JSON `id`) and is the reliable way to map a verdict back to the user's bibliography; it is absent on the claims[] path and on formats that carry no key. `status:'error'` means that one entry failed to verify, not that the batch failed. Entries appear in input order.
summaryNoCorpus roll-up: { total, matched, mismatch, ambiguous, not_found, errored, retracted }. `total` counts verifiable entries only, so it excludes `parseErrors` and anything past the cap. `retracted` is a separate axis from the verdict counts, and an entry can be both matched and retracted — never add the fields together.
truncatedNoCount of entries dropped beyond the 25-entry cap. Non-zero means the audit is incomplete — split the bibliography and call again for the rest.
parseErrorsNoEntries that could not be parsed or lacked a title: { index, error, message }. Same 1-based `index` space as `entries`, so the two arrays never collide: a given input position appears in exactly one of them. Report these to the user as unchecked, NOT as clean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • addedInput schema / properties / claims / items / properties / ads / description
      Added value: +"NASA ADS bibcode, e.g. '2019A&A...625A.135L'."
    • addedInput schema / properties / claims / items / properties / arxiv / description
      Added value: +"arXiv ID, e.g. '2301.00001' or 'arXiv:2301.00001'."
    • changedInput schema / properties / claims / items / properties / author / description
      Previous value: -"First-author family name as cited."New value: +"First-author family name as cited. Refines the comparison; a disagreement here can downgrade a verdict to 'ambiguous'."
    • addedInput schema / properties / claims / items / properties / container / description
      Added value: +"Journal or book title as cited. Refinement only, same role as `year`."
    • addedInput schema / properties / claims / items / properties / doi / description
      Added value: +"DOI as cited, with or without a prefix ('10.1038/nphys1170' or a doi.org URL)."
    • addedInput schema / properties / claims / items / properties / isbn / description
      Added value: +"ISBN-10 or ISBN-13; hyphens are tolerated."
    • addedInput schema / properties / claims / items / properties / issn / description
      Added value: +"ISSN of the containing journal. Identifies a container, not a paper, so it cannot resolve an entry on its own — supply it alongside another identifier."
    • addedInput schema / properties / claims / items / properties / pmcid / description
      Added value: +"PubMed Central ID, e.g. 'PMC1234567'."
    • addedInput schema / properties / claims / items / properties / pmid / description
      Added value: +"PubMed ID, digits only or 'PMID:' prefixed."
    • changedInput schema / properties / claims / items / properties / title / description
      Previous value: -"Title as cited. Required for each claim."New value: +"Title exactly as the citation claims it. Required — the audit compares this against the title of the record the identifier actually resolves to, and that comparison is the fabrication check."
    • addedInput schema / properties / claims / items / properties / whoIrisUrl / description
      Added value: +"WHO IRIS publication URL."
    • addedInput schema / properties / claims / items / properties / year / description
      Added value: +"Publication year as cited. Refinement only — it never decides a verdict alone."
    • changedOutput schema / properties / entries / description
      Previous value: -"One result per verifiable entry: { index, sourceKey?, status: 'ok'|'error', verdict, confidence, matched, mismatches, retraction, _provenance }."New value: +"One result per verifiable entry: { index, sourceKey?, status: 'ok'|'error', verdict, confidence, matched, mismatches, retraction, _provenance }. `index` is 1-BASED and counts position in the submitted input, so entry 1 is the first reference — do not add 1 again when you report it to a user. `sourceKey` is the entry's own key in the source file (BibTeX cite key, RIS `ID`, or CSL-JSON `id`) and is the reliable way to map a verdict back to the user's bibliography; it is absent on the claims[] path and on formats that carry no key. `status:'error'` means that one entry failed to verify, not that the batch failed. Entries appear in input order."
    • changedOutput schema / properties / parseErrors / description
      Previous value: -"Entries that could not be parsed or lacked a title: { index, error, message }."New value: +"Entries that could not be parsed or lacked a title: { index, error, message }. Same 1-based `index` space as `entries`, so the two arrays never collide: a given input position appears in exactly one of them. Report these to the user as unchecked, NOT as clean."
    • changedOutput schema / properties / summary / description
      Previous value: -"Corpus roll-up: { total, matched, mismatch, ambiguous, not_found, errored, retracted }."New value: +"Corpus roll-up: { total, matched, mismatch, ambiguous, not_found, errored, retracted }. `total` counts verifiable entries only, so it excludes `parseErrors` and anything past the cap. `retracted` is a separate axis from the verdict counts, and an entry can be both matched and retracted — never add the fields together."
    • changedOutput schema / properties / truncated / description
      Previous value: -"Count of entries dropped beyond the 25-entry cap."New value: +"Count of entries dropped beyond the 25-entry cap. Non-zero means the audit is incomplete — split the bibliography and call again for the rest."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint (read-only, idempotent, non-destructive). The description goes beyond this by revealing precedent: capping at 25 entries, truncation behavior, one-entry leniency (an error does not fail the batch), return structure with index and sourceKey semantics, and the distinction between summary fields mentioning retraction is a separate axis. It transparently discloses the limitation that it audits identity not support, which is valuable behavioral context.

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 lengthy but every sentence carries specific, actionable information—no filler. It front-loads the core purpose and the sibling relation, then moves into parameter semantics and return semantics. A bit verbose compared to a minimal definition, but the density of relevant detail justifies the length; structure is logical and well-paragraphed.

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?

This is a complex tool with 5 optional parameters, a detailed output schema, and nuanced behaviors (indexing, error handling, truncation, authentication). The description covers all critical: input selection, cap and truncation meaning, per-entry leniency, 1-based indexing, sourceKey PURPOSE, and the summary semantics with the retracted independent axis. With an output schema present, it also clarifies reading the verdict and error positions, making the description complete for correct invocation and interpretation.

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?

Though schema description coverage is 100%, the description adds deeper guidance for input selection: choosing between `bibliography` and `claims`, the auto-detection of format with an override, and the specific meaning of entries on each path. It also explains how the `checks` parameter behaves (defaults to retraction, pass [] to skip) and the gating for LLM screening, giving the agent richer understanding beyond the raw schema definitions.

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 audits a whole bibliography as a batch counterpart to verifyCitation, explaining exactly what the fabrication check does (real, resolvable identifier vs. non-matching title) plus retraction lookup. It explicitly positions it relative to verifyCitation and the sibling tools, so an agent knows exactly when this tool is distinct.

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?

The description provides concrete use cases ('when the user pastes a reference list... asks to audit my bibliography') and distinguishes input paths (bibliography vs claims), including the handling of truncated results and when to cancel the call. It clarifies what this tool does not do (does not check whether a source supports the claim) and references alternatives such as verifyCitation for single entries, giving a clear placement among siblings.

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
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