bib-enrich-mcp
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": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcp_enrich_bib_entryC | Enrich a bibliography entry by scraping metadata. Args: cite_key: The citation key for the entry title: Paper title to search for arxiv_id: arXiv ID (e.g., 2401.12345) doi: DOI of the paper Returns: BibTeX string with enriched metadata |
| mcp_enrich_bib_fileC | Enrich all entries in a BibTeX file. Args: file_path: Path to the .bib file Returns: Summary of enriched entries |
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 2 tools
The two tools have clearly distinct purposes: one enriches a single bibliography entry by accepting specific identifiers, while the other enriches all entries in a BibTeX file. No overlap in functionality.
Both tools follow a consistent naming pattern with the prefix 'mcp_enrich_bib_' followed by a specific suffix ('entry' and 'file'). The naming is uniform and predictable.
The server has only 2 tools, which is on the low end. For a focused enrichment task, this may be acceptable, but it feels slightly under-scoped compared to typical MCP servers that often offer 3-15 tools.
The server covers the core enrichment functionality but lacks additional tools for operations like searching for entries, validating BibTeX, or undoing enrichments. The surface is minimal and may leave agents with dead ends.