paper-preflight
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| S2_API_KEY | No | Semantic Scholar as a rescue source for references nobody else found. Optional; values are never printed or logged. | |
| OPENALEX_API_KEY | No | A larger OpenAlex budget for retraction checks. Optional; values are never printed or logged. | |
| PAPER_PREFLIGHT_EMAIL | No | Crossref'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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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, Use this first, on the whole paper. Use |
| 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_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
Use it when adding or replacing one entry; to check a whole bibliography use
|
| 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.
Use it after |
| preflight_cited_passagesA | For each sentence of the paper that cites 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 Use it only after |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
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.
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.
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.