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.

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.

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

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 and removes identifiers that point to another work. Show unsafe diffs to the user before applying them. References nobody could find are never "fixed".

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

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct action: verify references, explain a rule, look up a BibTeX entry, propose .bib diffs, and gather cited passages. The check/fix and check/cited_passages pairs are separated by verb (verify vs edit vs ground claims) and the descriptions reinforce the boundaries.

Naming Consistency5/5

All names share the preflight_ prefix and snake_case form with a predictable verb/noun tail (check, explain, bib_lookup, bib_fix, cited_passages). Minor sub-namespacing (bib_*) does not break the pattern.

Tool Count5/5

Five tools map cleanly onto the whole preflight workflow (check, explain, lookup, fix, evidence-gathering) with no redundancy. The count is well-scoped for the domain.

Completeness4/5

The surface covers verification, rule explanation, record lookup, repair diffs, and claim-to-passage grounding, which is most of a preflight lifecycle. There is no obvious way to enumerate all rules or configure/batch settings, a minor gap agents can work around.

Maintenance

ActivityMaintained
ResponsivenessNo issues