pubmed-mcp-server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_pubmedB | |
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 confusion or overlap between tools. The tool 'search_pubmed' has a clear, singular purpose of searching PubMed for articles, making disambiguation trivial.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'search_pubmed' follows a clear verb_noun pattern, and there are no other tools to compare it against for inconsistency.
A single tool for a PubMed server is too few for the apparent scope. PubMed typically involves operations like fetching article details, filtering by date or author, or retrieving citations, which are missing. This minimal set limits functionality and feels incomplete for the domain.
The tool set is severely incomplete for a PubMed server. While 'search_pubmed' covers basic searching, there are obvious gaps such as retrieving full article metadata, accessing citations, filtering results, or managing user queries. This will likely cause agent failures when more complex tasks are required.