Skip to main content
Glama
Sign In
Paper Search MCP

Paper Search MCP

by openags
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

download_hal

Download PDF documents from HAL repository using paper identifiers to access academic research papers for local storage and reference.

Instructions

Download PDF for a paper from HAL.

Args: paper_id: HAL paper identifier. save_path: Directory to save the PDF (default: './downloads'). Returns: str: Path to downloaded PDF.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "paper_id": "<paper_id>"
    },
    "name": "download_hal"
  }
}

Input Schema

NameRequiredDescriptionDefault
paper_idYes
save_pathNo./downloads

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states it downloads a PDF. It does not disclose error handling, authentication needs, rate limits, or behavior on missing papers.

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?

Concise and front-loaded with the core purpose, followed by parameter and return descriptions. No wasted words, but could organize args section more cleanly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple download operation and presence of an output schema, the description covers purpose, inputs, and output adequately. Minor gap: no mention of error scenarios.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description partially compensates by explaining paper_id as 'HAL paper identifier' and save_path as directory with default. However, it lacks details like ID format.

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?

The description clearly states the action ('Download PDF') and the resource ('paper from HAL'), distinguishing it from sibling download tools for other sources.

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 on when to use this tool versus alternatives like download_scihub or download_with_fallback. Usage is implied only by the source name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools