Skip to main content
Glama

adamamer20-paper-search-mcp-openai

by ai.smithery
OverviewDiscussionsAdmin

read_arxiv_paper

Read and extract text content from an arXiv paper PDF.

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: -"read_arxiv_paperArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "read_arxiv_paperOutput",
-  "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 full burden but fails to disclose critical behavioral traits: whether the extracted text is returned directly or written to 'save_path', what format the extraction produces, error handling for invalid paper IDs, or rate limiting concerns.

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 description is efficiently structured and front-loaded with the core action. However, given the lack of schema documentation and output schema, this conciseness results in under-specification rather than effective communication.

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 zero schema descriptions and no output schema, the description inadequately explains the two parameters or the return value (text content vs. file path). For a tool with sibling alternatives, the failure to contrast with 'download_arxiv' leaves significant context 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%, requiring the description to compensate. While 'from an arXiv paper PDF' implies 'paper_id' is an arXiv identifier, the description completely omits explanation of 'save_path' (its purpose, file format, or default behavior), leaving significant semantic gaps.

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 provides a clear verb ('Read and extract') and resource ('arXiv paper PDF'), distinguishing it from sibling 'download_arxiv' by specifying text extraction rather than file retrieval. However, it doesn't explicitly clarify the relationship with 'download_arxiv' or specify what 'read' means in terms of return values.

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 provided on when to use this tool versus 'download_arxiv' (which likely retrieves the raw PDF) or versus other academic source readers. No prerequisites mentioned regarding paper_id format or availability.

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