Skip to main content
Glama

adamamer20-paper-search-mcp-openai

by ai.smithery
OverviewDiscussionsAdmin

download_medrxiv

Download PDF of a medRxiv paper.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paper_idYes
save_pathNo./downloads

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / paper_id / title
      Removed value: -"Paper Id"
    • removedInput schema / properties / save_path / title
      Removed value: -"Save Path"
    • removedInput schema / title
      Removed value: -"download_medrxivArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "download_medrxivOutput",
-  "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?

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Download PDF' implies a filesystem write operation, the description omits critical details: idempotency, overwrite behavior, network dependencies, error handling for invalid IDs, and the fact that it saves to disk (implied only by the save_path parameter).

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 single sentence contains no fluff or redundancy. However, it borders on under-specification given the complete lack of schema descriptions and annotations, suggesting it is too concise for the information density required.

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?

Given two undocumented parameters (0% schema coverage), no output schema, and no annotations, the four-word description is insufficient. It fails to explain parameter semantics, return behavior, or error conditions necessary for correct invocation.

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%, requiring the description to compensate significantly. It implicitly suggests 'paper_id' refers to a medRxiv identifier by mentioning the source, but provides no information about expected ID formats (DOI vs medRxiv ID) and completely omits explanation of 'save_path' behavior or default values.

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 states a specific verb ('Download') and resource ('PDF of a medRxiv paper'), clearly identifying the tool's function. However, it does not explicitly distinguish from the sibling tool 'read_medrxiv_paper', leaving ambiguity about when to download versus read.

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?

The description provides no guidance on when to use this tool versus alternatives like 'read_medrxiv_paper' or 'fetch'. It fails to mention prerequisites such as obtaining a paper_id from search tools, or the expected workflow.

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