Skip to main content
Glama
enesjakozh
openags

Paper Search MCP

by openags
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

read_ssrn_paper

Retrieve academic paper content from SSRN using paper identifiers. Note: SSRN connector provides metadata only; full content reading is not supported.

Instructions

Read paper content from SSRN.

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

Args: paper_id: SSRN paper identifier. save_path: Directory where the PDF is/will be saved (unused). Returns: str: Error message from metadata-only SSRN connector.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paper_idYes
save_pathNo./downloads

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • paper_search_mcp/server.py:1238-1249 (handler)
    Handler function for read_ssrn_paper tool. Note that it actually invokes ssrn_searcher.read_paper, which is documented as metadata-only and does not support reading.
    async def read_ssrn_paper(paper_id: str, save_path: str = "./downloads") -> str:
    """Read paper content from SSRN.

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

    Args:
        paper_id: SSRN paper identifier.
        save_path: Directory where the PDF is/will be saved (unused).
    Returns:
        str: Error message from metadata-only SSRN connector.
    """
    return ssrn_searcher.read_paper(paper_id, save_path)
  • paper_search_mcp/server.py:1237-1238 (registration)
    Registration of read_ssrn_paper using the @mcp.tool() decorator.
    @mcp.tool()
async def read_ssrn_paper(paper_id: str, save_path: str = "./downloads") -> str:

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries full burden and excels at behavioral disclosure. It explicitly states the tool's limitation ('metadata-only and read is not supported'), reveals what the tool actually does (returns an error message), and explains parameter behavior ('save_path' is 'unused'). This provides crucial context beyond basic functionality.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is perfectly structured and front-loaded: the core purpose is stated first, followed by a critical note, then parameter explanations, and finally return value information. Every sentence earns its place with zero waste, making it highly efficient for an agent to parse.

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

Completeness5/5

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

Given the tool's complexity (it essentially always fails with an error message), no annotations, and 0% schema coverage, the description provides complete context. It explains the tool's actual behavior, parameter usage, and return value, and the output schema exists (confirming the string return type), making this description fully adequate for the agent's needs.

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

Parameters5/5

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

With 0% schema description coverage and 2 parameters, the description fully compensates by explaining both parameters: 'paper_id' is identified as 'SSRN paper identifier' and 'save_path' is explicitly noted as 'unused' with context about its purpose ('Directory where the PDF is/will be saved'). This adds significant meaning beyond the bare schema.

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 clearly states the action ('Read paper content from SSRN') and identifies the resource ('SSRN paper'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'download_ssrn' or 'search_ssrn' beyond the 'read' action, which is why it doesn't reach a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidance with the note: 'SSRN connector is metadata-only and read is not supported.' This clearly indicates when NOT to use this tool (when expecting actual paper content) and sets expectations about its limitations, making it highly effective for guiding agent decisions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/openags/paper-search-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server