Skip to main content
Glama

adamamer20-paper-search-mcp-openai

by ai.smithery
OverviewDiscussionsAdmin

download_arxiv

Download PDF of an arXiv 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_arxivArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "download_arxivOutput",
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral disclosure. While it specifies the PDF format, it omits critical side effects (file system writes), idempotency concerns (overwriting existing files), and the return value (file path vs. binary content). Lacks safety disclosures expected for a file-download operation.

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

Conciseness3/5

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

The single sentence is efficient with no wasted words, but the overall description is inappropriately terse given the lack of schema documentation and annotations. It prioritizes brevity over necessary operational detail.

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?

Incomplete for a file-system-mutating tool. Without an output schema, the description should explain what is returned (e.g., local file path). Missing safety context regarding disk writes and no mention of error conditions (e.g., invalid paper ID, network failure).

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

Parameters1/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 for undocumented parameters. It fails to do so, providing no guidance on the `paper_id` format (e.g., '2101.00001' vs. URL) or the `save_path` behavior (default location, directory creation).

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 specific verb (Download) and resource (PDF of an arXiv paper), clearly identifying the target domain. However, it fails to differentiate from the sibling tool `read_arxiv_paper`, leaving ambiguity about whether this saves a file to disk versus extracting text content.

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 `read_arxiv_paper` alternative or other download sources. Does not mention prerequisites such as valid arXiv ID formats or directory permissions for the save_path.

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