Skip to main content
Glama

find_reviews

Retrieve systematic reviews and meta-analyses from PubMed filtered by relevance to a query.

Instructions

Search PubMed for systematic reviews and meta-analyses only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
max_resultsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • server.py:60-64 (handler)
    The handler function for the 'find_reviews' MCP tool. It filters PubMed searches to systematic reviews and meta-analyses by appending a filter to the query and delegating to search_pubmed.
    async def find_reviews(query: str, max_results: int = 10) -> str:
        """Search PubMed for systematic reviews and meta-analyses only."""
        return await search_pubmed(
            f"{query} AND (systematic review[pt] OR meta-analysis[pt])", max_results
        )
  • server.py:59-59 (registration)
    The '@mcp.tool()' decorator that registers 'find_reviews' as an MCP tool with FastMCP.
    @mcp.tool()
  • The function signature defines the input schema: 'query: str' (required) and 'max_results: int = 10' (optional with default). The return type annotation '-> str' defines the output schema.
    async def find_reviews(query: str, max_results: int = 10) -> str:
        """Search PubMed for systematic reviews and meta-analyses only."""
        return await search_pubmed(
            f"{query} AND (systematic review[pt] OR meta-analysis[pt])", max_results
  • The 'search_pubmed' helper function that 'find_reviews' delegates to. It performs the actual PubMed E-utilities API call (esearch + esummary) and returns formatted results.
    @mcp.tool()
    async def search_pubmed(query: str, max_results: int = 10) -> str:
        """Search PubMed by keyword, MeSH term, or author. Returns PMIDs and titles."""
        async with httpx.AsyncClient() as client:
            r = await client.get(f"{PUBMED_BASE}/esearch.fcgi", params={
                "db": "pubmed", "term": query, "retmax": max_results,
                "retmode": "json"
            })
            data = r.json()
            ids = data["esearchresult"]["idlist"]
            r2 = await client.get(f"{PUBMED_BASE}/esummary.fcgi", params={
                "db": "pubmed", "id": ",".join(ids), "retmode": "json"
            })
            summaries = r2.json()["result"]
            results = []
            for pmid in ids:
                title = summaries[pmid]["title"]
                results.append(f"PMID {pmid}: {title}")
            return "\n".join(results)
Behavior3/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. It adds the constraint 'only' to indicate filtering to reviews, which is useful. However, it does not disclose other behavioral traits like rate limits, pagination, or output format.

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?

The description is a single sentence, efficient and front-loaded with the tool's purpose. However, it could be slightly more structured by including parameter hints.

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?

Given the existence of an output schema, the description need not explain return values. However, it lacks parameter semantics and usage guidelines. It is adequate for a simple tool but has clear gaps.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not explain any parameters (query, max_results). The agent must infer their meaning from the schema alone, which is insufficient.

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 'Search PubMed for systematic reviews and meta-analyses only', which is a specific verb+resource. This distinguishes it from sibling tools like search_pubmed (general search) and get_abstract (fetching abstracts).

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 is provided on when to use this tool versus alternatives (e.g., search_pubmed). The description does not mention context, prerequisites, or exclusions.

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

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/pubspro/pubmed-search'

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