Skip to main content
Glama
Sign In
PaperGraph MCP

PaperGraph MCP

by lotchuazzz-crypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

workspace_record_reading_checkpoint

Record or update reading checkpoints in PaperGraph MCP's active workspace to track paper reading progress and status for a session target.

Instructions

Create or update a reading checkpoint in the active workspace.

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": {
      "session_id": "<session_id>",
      "target_kind": "<target_kind>",
      "target_id": "<target_id>",
      "status": "<status>"
    },
    "name": "workspace_record_reading_checkpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYes
summaryNo
evidenceNo
target_idYes
session_idYes
target_kindYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.2
    • addedInput schema / properties / target_kind / enum
      Added value: +[
+  "result_id",
+  "proof_id",
+  "span_id",
+  "external_stop",
+  "unresolved_stop"
+]
  2. Addedv0.9.3

TDQS

C2.6/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. 'Create or update' implies upsert semantics, but the description does not disclose whether this is idempotent, what happens to a pre-existing checkpoint on update, what permissions or session state are required, or what is returned.

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

Conciseness3/5

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

A single efficient, front-loaded sentence with no padding. It is concise, but the brevity reflects under-specification rather than tight expression, so it lands at a bare-minimum 3.

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 mutation tool with six parameters, zero schema coverage, no annotations, no output schema, and an enum-typed target_kind, this one sentence is far too thin. The critical enum values and required-field semantics are left entirely unexplained.

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% across six parameters, so the description must compensate and does not. It never explains session_id scoping, target_kind/target_id pairing, the meaning of the status string, or the optional summary/evidence fields.

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?

States a specific verb ('create or update') and resource ('reading checkpoint in the active workspace'), so the operation type is identifiable. However, 'reading checkpoint' is undefined domain jargon and the description does nothing to distinguish this from sibling concepts like reading sessions, queues, notes, or paths.

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 and no alternative named. An agent cannot tell whether a checkpoint belongs to a reading session, when to record one versus calling workspace_add_reading_note, or what prerequisite (an existing session) is needed.

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