Skip to main content
Glama
Sign In
scipdf-mcp

scipdf-mcp

by gjjisadog
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_papers

Retrieve a list of downloaded academic papers from the specified directory, ordered by date (newest first).

Instructions

List PDF files already in the download directory (most recent first).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_papers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax files (default 50)
outdirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It states the tool lists files but does not mention side effects (e.g., is it read-only? Does it modify anything?), permissions, or error handling (e.g., what if the directory is missing?). This is insufficient.

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 a single, concise sentence that immediately conveys the core action and ordering. However, it could be slightly improved by front-loading the key benefit (listing PDFs) without sacrificing brevity.

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 no output schema and only 50% schema description coverage, the description should compensate with details about return format, default behavior, and limitations. It does not mention response structure, pagination, or behaviors like empty directory handling, leaving significant 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?

The schema covers 50% of parameters: 'limit' has a description, but 'outdir' has none. The description adds no new meaning beyond the schema—it does not explain what 'outdir' represents or default directory behavior. For an agent, this is 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?

The description clearly states the verb ('List'), the resource ('PDF files already in the download directory'), and the ordering ('most recent first'). It distinguishes itself from sibling tools like 'download_paper' (downloads) and 'list_mirrors' (lists mirrors), making the purpose unambiguous.

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 is provided on when to use this tool versus alternatives. For example, it does not mention that this tool only lists existing files, while 'download_paper' fetches new ones. The description lacks any contextual cues for selection.

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