Skip to main content
Glama

adamamer20-paper-search-mcp-openai

by ai.smithery
OverviewDiscussionsAdmin

search_pubmed

Search academic papers from PubMed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / max_results / title
      Removed value: -"Max Results"
    • changedInput schema / properties / max_results / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"search_pubmedArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "search_pubmedOutput",
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

C2.7/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 fails to specify what the tool returns (PMIDs, abstracts, metadata?), whether it performs live API calls, or pagination behavior. The description only confirms an external search occurs.

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?

Extremely concise with zero redundant words or filler. However, it is under-specified rather than efficiently complete. The single sentence structure is appropriate but lacks the necessary density of information for a tool with zero schema documentation.

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

Completeness2/5

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

Inadequate given the lack of output schema and 0% parameter coverage. The description should explain return values (citation list vs full text) and parameter details, but provides neither. For a search tool with 2 parameters and no return schema, the description is insufficient.

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% (neither 'query' nor 'max_results' have descriptions), yet the description does not compensate. It fails to document the default value of 10 for max_results, expected query syntax (PubMed query grammar), or that results are limited/bounded.

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?

States a clear verb ('Search') and resource ('academic papers from PubMed'), distinguishing it from sibling search tools by specifying the PubMed source. However, it misses the opportunity to clarify that PubMed specializes in biomedical/life sciences literature, which would help agents select it over search_arxiv or search_google_scholar.

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?

Provides no guidance on when to use this tool versus the 16 other search/download siblings. Does not mention prerequisites, rate limits, or that PubMed requires specific query syntax. Agents cannot determine if this is preferable to search_google_scholar or read_pubmed_paper.

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

All adamamer20-paper-search-mcp-openai toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources