preprint-fulltext
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_preprintsB | Search preprint full text (Europe PMC relevance or OpenAlex n-gram). field scopes to fulltext|title|abstract|author. |
| get_fulltextC | Retrieve structured full-text sections for a preprint DOI (or URL). Resolves to the latest version by default; pass version for a specific one. |
| get_metadataB | Retrieve bibliographic metadata (abstract only) for a preprint DOI. |
| resolveB | Resolve between a DOI, an OpenAlex id, and a Europe PMC PPR id. |
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 4 tools
Each tool has a clearly distinct purpose: search_preprints for searching, get_fulltext for retrieving full text, get_metadata for bibliographic metadata, and resolve for ID conversion. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case (search_preprints, get_fulltext, get_metadata). 'resolve' is a single verb but fits the pattern of concise, predictable naming.
With 4 tools, the server is well-scoped for its domain. Each tool serves a core function without being under- or over-provisioned, making it easy for agents to navigate.
The tool surface covers the essential operations for preprint fulltext retrieval: searching, full-text access, metadata retrieval, and ID resolution. There are no obvious gaps or dead ends.