Skip to main content
Glama
Sign In
PubMed MCP Server

PubMed MCP Server

by Augmented-Nature
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_by_mesh_terms

Search PubMed citations by Medical Subject Headings (MeSH) terms. Optionally limit results to articles where terms are major topics.

Instructions

Search using Medical Subject Headings (MeSH) terms

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mesh_terms": "<mesh_terms>"
    },
    "name": "search_by_mesh_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
mesh_termsYesMeSH terms to search for
major_topic_onlyNoOnly return articles where MeSH term is a major topic (default: false)
max_resultsNoMaximum results (default: 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, and description only says 'search'. No disclosure of read-only nature, result ordering, or pagination behavior.

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

Conciseness4/5

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

Single sentence that is direct and efficient. Could benefit from a brief additional sentence on usage.

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

Completeness3/5

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

No output schema; description does not explain return format, pagination, or limitations. Adequate for a simple search but missing details.

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

Parameters3/5

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

Schema provides 100% description coverage for all three parameters. Description adds minimal value beyond repeating the MeSH concept.

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

Purpose4/5

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

The description clearly states the tool searches using MeSH terms. It distinguishes from sibling tools like search_articles by specifying the controlled vocabulary, but could be more explicit about returning articles.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs. siblings like advanced_search or search_by_author. No mention of prerequisites or context.

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

Deploy Server

Other Tools