Skip to main content
Glama
amos689

paper-preflight

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
S2_API_KEYNoSemantic Scholar as a rescue source for references nobody else found. Optional; values are never printed or logged.
OPENALEX_API_KEYNoA larger OpenAlex budget for retraction checks. Optional; values are never printed or logged.
PAPER_PREFLIGHT_EMAILNoCrossref's polite pool: faster, more reliable lookups. Optional; values are never printed or logged.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
preflight_checkA

Verify every cited reference of a LaTeX project (or a .bib file) against real scholarly records, and check citation keys and the bibliography.

Returns a summary (error/warning counts, one verdict per reference, whether the run was complete) and the findings, most severe first, max_findings at a time; call again with offset=next_offset for more. complete: false means a source was unavailable, so the paper cannot be declared clean yet. offline: true answers from the local cache only. The first run of a paper may take a minute or two (progress is reported while the references are searched); later runs are served from the cache.

Use this first, on the whole paper. Use preflight_explain to understand a finding, preflight_bib_fix to get the corrections as a diff, and preflight_bib_lookup to get a single entry.

preflight_explainA

Explain a paper-preflight rule (for example REF003 or CIT001): what it detects, its default severity, the message template and whether a fix can be applied safely. Use it when a finding from preflight_check is unclear; it does not look at the paper.

preflight_bib_lookupA

Get a BibTeX entry for a DOI, an arXiv ID or a title, built from the registry record instead of written from memory. Give identifier, or title (with author and year when you know them).

status is "found" (use bibtex as is), "ambiguous" (several works match: pick from candidates with the user, or retry with author/year), "not_found" (ask the user for the source; do not invent one) or "unavailable" (a source did not answer; retry later). A published preprint comes back as its published version with the eprint kept; status_flags lists notices such as "retracted".

Use it when adding or replacing one entry; to check a whole bibliography use preflight_check.

preflight_bib_fixA

Propose edits to the .bib files, taken from the verified records, as a unified diff. Nothing is written: apply the diff with your own editing tools.

level="safe" only fixes identifiers written so that links break and adds DOIs the registry has; level="unsafe" also rewrites authors, title, year and venue from the record, removes identifiers that point to another work and cites a preprint as its published version (keeping the eprint). Show unsafe diffs to the user before applying them. References nobody could find are never "fixed".

Use it after preflight_check has reported errors or warnings in the bibliography.

preflight_cited_passagesA

For each sentence of the paper that cites key: the claim it makes and the passages of the cited work ranked best for that claim, for you to judge whether the work supports it. The first call downloads the work's text (its arXiv source, an open-access full text or PDF, or else its abstract) into the local cache.

Judge each claim conservatively. Say "confirmed" only when a passage states it (quote the passage word for word) or, for a citation set right after a name such as "Adam \cite{...}", when name_in_title is true. Otherwise say "could not confirm", with the reason: no text, only the abstract, or no passage says it. Never call a citation wrong or invented on this evidence: the text may say it in other words, or be only an abstract. evidence.level is "full_text", "abstract" or "none".

Use it only after preflight_check has verified that the work exists; it answers whether a real work supports a sentence, not whether the reference is correct.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.7/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a genuinely distinct action: whole-paper verification (check), rule explanation (explain), single-entry retrieval (bib_lookup), diff generation (bib_fix), and claim-support evidence (cited_passages). The descriptions explicitly cross-reference each other and clarify scope boundaries (e.g. 'to check a whole bibliography use preflight_check'). No two tools overlap in purpose.

Naming Consistency5/5

All tools use a consistent 'preflight_' prefix followed by a snake_case noun/verb pattern (preflight_check, preflight_explain, preflight_bib_lookup, preflight_bib_fix, preflight_cited_passages). The convention is predictable and readable throughout, with no style mixing.

Tool Count5/5

Five tools is well-scoped for a reference-preflight service, and each maps to a clear stage of the workflow (verify, explain, lookup, fix, judge support). Nothing feels redundant or missing at the count level.

Completeness4/5

The surface covers the full lifecycle: whole-paper check, rule explanation, single-entry lookup, safe/unsafe fixes, and citation-support evidence. Minor gaps exist (e.g. no bulk bibliography export or cache-management tool), but agents can work around them and core workflows are complete.

Maintenance

ActivityMaintained
ResponsivenessNo issues