mcp-simple-pubmed
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUBMED_EMAIL | Yes | Your email address (required by NCBI) | |
| PUBMED_API_KEY | No | Optional API key for higher rate limits (10 requests/second instead of 3 requests/second) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_pubmedA | Search PubMed for medical and life sciences research articles. You can use these search features:
Examples:
The search will return:
Note: Use quotes around multi-word terms for best results. |
| get_paper_fulltextA | Get full text of a PubMed article using its ID. This tool attempts to retrieve the complete text of the paper if available through PubMed Central. If the paper is not available in PMC, it will return a message explaining why and provide information about where the text might be available (e.g., through DOI). Example usage: get_paper_fulltext(pmid="39661433") Returns:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| systematic_review_search | Generate a systematic review search strategy for a medical topic. |
| pico_search | Build a PICO-based search query for clinical questions. |
| author_search | Find all publications by a specific author. |
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: get_paper_fulltext retrieves the full text of a specific article by ID, while search_pubmed performs keyword-based searches across the PubMed database. There is no overlap or ambiguity between these functions.
Both tools follow a consistent verb_noun naming pattern: get_paper_fulltext and search_pubmed. The naming is clear and predictable, with no deviations in style or convention.
With only two tools, the server feels thin for a PubMed interface, as it lacks operations like fetching paper metadata, filtering search results, or managing citations. While the tools cover basic retrieval and search, more comprehensive coverage would typically require additional tools.
The tool set is significantly incomplete for a PubMed domain. It lacks essential operations such as get_paper_metadata (for details like authors, journal, abstract without full text), filter_search_results, or citation-related tools. This will likely cause agent failures when trying to perform common PubMed tasks beyond simple search and full-text retrieval.