MCP PubMed Search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENTREZ_EMAIL | Yes |
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 |
|---|---|
| pubmed_searchC | Search PubMed medical literature database |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool's purpose is clearly defined as searching the PubMed database, leaving no room for misselection.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The tool name 'pubmed_search' follows a clear verb_noun pattern that is appropriate for its function.
One tool is too few for a server named 'MCP PubMed Search', which suggests a broader scope for interacting with PubMed. A single search tool feels thin and incomplete, lacking operations like filtering results, retrieving article details, or managing queries.
The tool surface is severely incomplete for a PubMed search domain. While searching is a core function, there are obvious gaps such as no ability to get article metadata, filter searches, save results, or handle citations, which limits agent workflows significantly.