Skip to main content
Glama
cyanheads

pubmed-mcp-server

by cyanheads

Pubmed Lookup Mesh

pubmed_lookup_mesh
Read-only

Retrieve MeSH descriptor records with tree numbers, scope notes, and entry terms. Supports pagination for large result sets.

Instructions

Search and explore the MeSH (Medical Subject Headings) controlled vocabulary. Returns descriptor records with tree numbers, scope notes, and entry terms, plus pagination via offset for paging past the maxResults cap.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesMeSH descriptor name or free-text term to look up
offsetNoResult offset for pagination (0-based). Pass the `nextOffset` from the previous response to get the following page; the exact-descriptor match is pinned to the first page only.
maxResultsNoMaximum results
includeDetailsNoFetch full MeSH records (scope notes, tree numbers, entry terms)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesOriginal search query
noticeNoOptional guidance when no descriptors matched or the offset overshot the result set — suggests spell-check, free-text search, or resetting the offset. Absent on successful result pages.
offsetYesResult offset this page was read from
resultsYesMatching MeSH records
nextOffsetNoOffset to request for the next page. Omitted when this is the last page, so its absence is the end-of-results signal.
totalCountYesTotal MeSH descriptors matching the query upstream, before the maxResults cap
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating a safe read operation. The description adds behavioral context by detailing what is returned (descriptor records with specific fields) and pagination via offset. No contradictions; it complements the annotations well.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief (two sentences) yet comprehensive. It front-loads the purpose and immediately provides key details about returns and pagination. Every sentence adds value; no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the annotations, full schema coverage, and presence of output schema, the description covers all essential aspects: what the tool does, what it returns, and how pagination works. It is complete for a lookup tool with these structured supports.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the description adds significant value beyond the parameter descriptions. It explains that offset is for pagination and that the exact-descriptor match is pinned to the first page. It also specifies what includeDetails controls (scope notes, tree numbers, entry terms). This enriches understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: searching and exploring the MeSH controlled vocabulary. It specifies the resource (MeSH), the verb (search/explore), and the return type (descriptor records with tree numbers, scope notes, entry terms). This distinguishes it from sibling tools like pubmed_search_articles which search articles, not vocabulary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to use or when not to use this tool. It implies usage for MeSH term lookup, but no alternatives or exclusions are mentioned. Given sibling tools like pubmed_search_articles, the context helps, but the description lacks direct guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cyanheads/pubmed-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server