PubMed Advanced MCP Server

advanced_search

Build complex PubMed search queries with field-specific terms, Boolean operators, and date filters.

Instructions

Build complex Boolean queries with field-specific search.

Provides precise control over search logic with multiple terms, fields, and Boolean operators.

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": {
      "query_builder": "<query_builder>"
    },
    "name": "advanced_search"
  }
}

Input Schema

Name	Required	Description	Default
`date_field`	No	"publication_date" or "entry_date"	publication_date
`max_results`	No	Number of results
`query_builder`	Yes	List of search terms, each with: - field: "title", "abstract", "author", "journal", "all_fields", "mesh" - term: The search term - operator: "AND", "OR", "NOT"
`date_range_end`	No
`date_range_start`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 6, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention any behavioral traits such as read-only nature, rate limits, error conditions, or what the response contains. The description only states what the tool does, not how it behaves or any side effects.

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 concise and front-loaded: two sentences that immediately state the core purpose and value. Every word earns its place, with no redundant or filler content.

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?

The tool has an output schema, so return value documentation is not a burden on the description. However, the description lacks context about when to use this tool versus simpler search tools, and it does not provide examples or clarify the structure of the query_builder beyond what the schema already states. Given the tool's moderate complexity, the description is minimally sufficient but leaves gaps.

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?

The input schema covers 60% of the parameters with descriptions (e.g., query_builder field/term/operator, date_field options). The description adds minimal extra meaning beyond the schema, mentioning 'multiple terms, fields, and Boolean operators' but not detailing the specific parameters or their composition. Since schema coverage is moderate, the description does not significantly compensate for missing parameter details.

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 with a specific verb ('Build') and resource ('complex Boolean queries with field-specific search'). It distinguishes itself from sibling tools like global_search and pubmed_search by emphasizing complex Boolean logic and field-specific control.

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 implies use for complex queries requiring Boolean operators and field-specific search, but it does not explicitly state when to use this tool over alternatives, nor does it mention exclusions or alternatives. The usage context is implied but not directly articulated.

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

Deploy Server