Skip to main content
Glama

adamamer20-paper-search-mcp-openai

by ai.smithery
OverviewDiscussionsAdmin

read_biorxiv_paper

Read and extract text content from a bioRxiv 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_biorxiv_paperArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "read_biorxiv_paperOutput",
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description carries full disclosure burden. Mentions 'extract text content' indicating the return type, but fails to clarify if the PDF is temporarily downloaded, what format the extracted text takes, or whether 'save_path' stores the PDF or the extracted text. Missing mutation/safety disclosure.

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?

Single 9-word sentence is efficiently front-loaded with action verbs. No redundant phrases, though extreme brevity contributes to information gaps given the lack of schema documentation and annotations.

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 for a 2-parameter tool with zero schema descriptions and no output schema. Given the complexity of academic paper processing and the rich sibling tool ecosystem, the description should explain parameter relationships (e.g., paper_id sourced from search) and output format, which it does not.

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 has 0% description coverage, requiring description compensation. Implicitly identifies 'paper_id' as referring to bioRxiv papers, but provides no format guidance (DOI vs. bioRxiv ID). Completely omits 'save_path', leaving its purpose (PDF caching vs. text output directory) ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb phrase 'Read and extract text content' combined with specific resource 'bioRxiv paper PDF' clearly defines the scope. Effectively distinguishes from sibling 'download_biorxiv' (extraction vs. file saving) and from 'search_biorxiv' (processing specific ID vs. discovery), as well as domain-specific variants like 'read_arxiv_paper'.

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 explicit guidance on when to use this versus 'download_biorxiv' or prerequisites like obtaining paper_id from 'search_biorxiv'. While the name implies usage, the description lacks when/when-not instructions critical for an agent choosing between 20+ similar academic paper tools.

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