PaperGraph MCP

workspace_list_results

List paginated theorem results by limit and offset, then advance offset by returned count until a page has fewer than limit items. Browse stable pages without assuming a complete list.

Instructions

List a stable result page (limit 1..100). Advance offset by returned count.

A full page may be truncated; continue until a page has fewer than limit results. This is not an unbounded complete list.

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_list_results"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	No
`limit`	No
`offset`	No
`paper_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.2.2Oct 17, 2026
- addedInput schema / properties / limit / maximum
```
Added value: +100
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- addedInput schema / properties / offset
```
Added value: +{
+  "default": 0,
+  "minimum": 0,
+  "title": "Offset",
+  "type": "integer"
+}
```
Addedv0.9.3Sep 8, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: pages are 'stable', a full page may be truncated, and the tool is explicitly not an unbounded complete list. That is genuinely useful, but it says nothing about return shape, filtering effects, or any auth/workspace preconditions.

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?

Short and front-loaded: the pagination contract is stated in the first sentence and the continuation rule immediately after. Every sentence earns its place, though the awkward line breaks add no structure.

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?

An output schema exists so return values needn't be explained, and pagination is covered well. But for a 4-parameter listing tool with 0% schema description coverage, the unexplained 'kind' and 'paper_id' filters are a real gap an agent cannot close from any other field.

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% for 4 parameters. The description only restates the limit range (already enforced by schema min/max) and the offset advance rule; the 'kind' and 'paper_id' parameters receive no explanation anywhere, leaving half the surface opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb ('List') and resource ('result page'), and the pagination framing tells the agent this is a paged enumeration. However, 'result' is never disambiguated against siblings like workspace_get_result or workspace_list_papers, and the sibling set is large, so the agent gets only an implied sense of what a 'result' actually is here.

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

Usage Guidelines3/5

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

It gives real procedural guidance for pagination: advance offset by returned count and stop when a page is shorter than limit. It does not say when to prefer this tool over alternatives (e.g., workspace_get_result for a single result) or what the kind/paper_id filters are for.

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

Deploy Server