Skip to main content
Glama
Sign In
PaperGraph MCP

PaperGraph MCP

by lotchuazzz-crypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

workspace_resolve_external_reference

Resolve blocked external references by assigning a user-confirmed target, restoring accurate theorem dependency links.

Instructions

Resolve a blocked external reference to a user-confirmed target.

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>",
      "blocked_id": "<blocked_id>",
      "target": "<target>"
    },
    "name": "workspace_resolve_external_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes
paper_idYes
blocked_idYes
artifact_dirNo
import_targetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.3

TDQS

C2.4/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It only says 'resolve', which implies an action, but doesn't disclose side effects, reversibility, permissions, or return value. Minimal behavioral info.

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?

It is a single sentence, very concise, but it lacks structure and any detail. It's not verbose, but it's under-specified. For conciseness alone, it's okay, but it doesn't earn its place because it doesn't provide value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 5 parameters, one nested object, no output schema, and no annotations, this description is grossly insufficient. It doesn't explain what a blocked external reference is, what the target object should contain, or what happens after resolution.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and description doesn't explain any parameters. Only 'target' is mentioned in prose but without meaning. No help for agent to fill paper_id, blocked_id, or import_target.

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 'resolve' and resource 'blocked external reference', and mentions 'user-confirmed target' which implies a confirmation step. However, it doesn't differentiate from sibling workspace_resolve_external_reference_candidate, which likely handles candidates. So the purpose is clear but lacks sibling distinction.

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 on when to use this vs alternatives. The description doesn't mention any context like prerequisites, or that it should be used after a search or candidate resolution. An agent has no way to know when to invoke this tool.

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