Skip to main content
Glama
Sign In
PaperGraph MCP

PaperGraph MCP

by lotchuazzz-crypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

workspace_get_source_slice

Fetch bounded source text around a specified span, result, or proof ID in a mathematical paper, so you can inspect theorem context and dependencies.

Instructions

Return bounded source text around one span, result, or proof.

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

Input Schema

NameRequiredDescriptionDefault
contextNo
span_idNo
proof_idNo
result_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.2
    • addedInput schema / properties / context / maximum
      Added value: +5
    • addedInput schema / properties / context / minimum
      Added value: +0
  2. Addedv0.9.3

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and falls short. 'Bounded' gestures at a limit but never says what binds it, whether exactly one ID is required or expected, or what happens when zero or multiple IDs are supplied across four optional parameters.

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 tight clause with the verb and scope front-loaded and no filler. It is efficient, though the brevity contributes to the under-specification noted elsewhere rather than being purely a virtue.

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 output schema, no annotations, and four undocumented parameters, the description should explain the return shape (raw source text?), how far the slice extends, and the ID-selection rule. None of that is present, leaving the agent to guess at invocation semantics.

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 four parameters with no required fields, so the description must compensate. It does map span_id/result_id/proof_id to their targets, which is useful, but the 'context' parameter (an integer, 0-5, default 1) is left entirely unexplained and the mutual exclusivity of the three IDs is not stated.

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 states a specific verb ('Return') and resource ('bounded source text around one span, result, or proof'), and the three nouns map to the three ID parameters. However, it never distinguishes itself from sibling workspace_read_source_blocks, so an agent cannot tell which retrieval tool to reach for without opening both.

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 exclusions, and no alternative named. The phrase 'one span, result, or proof' hints at accepted input kinds but does not say when this tool is preferable to workspace_read_source_blocks or workspace_get_result_proof.

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