Skip to main content
Glama

adamamer20-paper-search-mcp-openai

by ai.smithery
OverviewDiscussionsAdmin

download_crossref

Attempt to download PDF of a CrossRef 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_crossrefArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "download_crossrefOutput",
-  "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?

With no annotations provided, the description carries full burden but only discloses fallibility ('Attempt'). It omits critical behavioral details: file system side effects (directory creation, overwrites), return value format (file path? success boolean?), and CrossRef API interaction details.

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 front-loaded with the core action and wastes no words, earning a baseline score. However, given the tool's complexity (file I/O, external API, 2 undocumented parameters), the description is inappropriately brief rather than efficiently concise.

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 high complexity (file system mutation, 20+ sibling tools with overlapping domains, zero schema documentation, no output schema), the description is insufficient. It lacks parameter specifications, output contract, and error handling guidance necessary for safe invocation.

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%, yet the description fails to compensate. It does not explain what 'paper_id' accepts (DOI? CrossRef internal ID?) or mention the 'save_path' parameter and its default './downloads' behavior, leaving both parameters effectively undocumented.

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 uses specific verb 'download' and resource 'PDF of a CrossRef paper', clearly identifying the action and target. However, it could better distinguish from sibling 'read_crossref_paper' regarding whether this saves to disk versus returns 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?

The word 'Attempt' hints at potential failure modes (PDF unavailable, network errors), but provides no explicit guidance on when to use this versus 'read_crossref_paper' or 'get_crossref_paper_by_doi', nor prerequisites like write 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