Skip to main content
Glama
Sign In
PaperGraph MCP

PaperGraph MCP

by lotchuazzz-crypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

workspace_export_paper_reading_report

Export a deterministic Markdown reading report for one stored paper, summarizing its theorem dependencies for review.

Instructions

Export a deterministic Markdown reading report for one stored paper.

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": "workspace_export_paper_reading_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
paper_idYes
max_candidatesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.2
    • addedInput schema / properties / max_candidates / maximum
      Added value: +20
    • addedInput schema / properties / max_candidates / minimum
      Added value: +1
  2. Addedv0.11.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose two traits beyond the schema — the output is Markdown and it is deterministic — but it says nothing about whether the export writes to disk or returns inline, whether it is read-only, how large the output may be, or how it behaves if the paper is missing.

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?

A single front-loaded sentence with no filler. It is efficient, though the brevity partly reflects under-specification rather than disciplined trimming.

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?

With no annotations, no output schema, and 0% parameter documentation, this one-liner is too thin for a two-parameter export tool. The Markdown/deterministic detail partially covers the return value, but the meaning of max_candidates and the file-vs-inline behavior remain unaddressed.

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 description coverage is 0% and the description mentions neither parameter. paper_id is at least inferable from 'one stored paper', but max_candidates is entirely unexplained — what candidates are being capped, and how the cap affects the report, is left to guesswork.

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 gives a specific verb (export) plus resource (Markdown reading report) and scope (one stored paper), which is clear enough to distinguish it from read-oriented siblings like workspace_get_paper. However, it does not differentiate itself from near-neighbors such as workspace_export_reading_bundle or workspace_export_reading_session_summary, leaving the agent to guess which export to pick.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. With five other export-family tools in the sibling list, the absence of any routing signal is a real gap.

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