Skip to main content
Glama
Sign In
Paper Search MCP

Paper Search MCP

by openags
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

download_ssrn

Download PDFs for academic papers from SSRN using paper identifiers. Note: SSRN connector provides metadata only and does not support actual file downloads.

Instructions

Download PDF for a paper from SSRN.

Note: SSRN connector is metadata-only and download is not supported.

Args: paper_id: SSRN paper identifier. save_path: Directory to save the PDF (unused). Returns: str: Error message from metadata-only SSRN connector.

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_ssrn"
  }
}

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

C2.7/5.0
Behavior3/5

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

The description discloses the tool returns an error message, but the first sentence implies a download capability, misleading the agent. No annotations provided.

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 description is short and to the point, but the contradictory first sentence could be reworded for clarity.

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?

For a tool that always fails, the description does not explain why or what to use instead, leaving the agent without a clear alternative.

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

Parameters4/5

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

With 0% schema description coverage, the description adds value by explaining paper_id and explicitly noting save_path is unused, which the schema does not convey.

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

Purpose2/5

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

The description states 'Download PDF for a paper from SSRN' but immediately contradicts with 'SSRN connector is metadata-only and download is not supported', creating confusion about the tool's actual purpose.

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 vs alternatives like download_arxiv or read_ssrn_paper. The note about metadata-only hints at unsuitability but doesn't name a substitute.

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