okraPDF PDF MCP server

Official

Overview Schema Source Related Servers Discussions Admin

Poll document view

poll_document_view

Refreshes the PDF viewer for a document: updates upload/parse/render status, page images, and extracted blocks. Use to synchronize the view with current processing state.

Instructions

Internal: the viewer widget refreshes upload/parse/render status, page images, and extracted blocks. Not for direct agent use.

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": {
      "document_id": "<document_id>",
      "view_uuid": "<view_uuid>"
    },
    "name": "poll_document_view"
  }
}

Input Schema

Name	Required	Description
`pages`	No	Pages to refresh, using the same range/list syntax as view_document. Defaults to the first 3 pages.
`view_uuid`	Yes	The open viewer view_uuid from upload_document or view_document.
`document_id`	Yes	okraPDF document ID being viewed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

A3.5/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 burden. It discloses only that the tool is internal and what it refreshes, but gives no indication of side effects, return values, or behavior when called. This is insufficient transparency for a tool that agents might encounter.

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?

The description is only two sentences and immediately front-loads the critical 'Internal' label. It is efficient with words, though it could be slightly more structured to separate the function from the usage restriction.

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?

The tool has no output schema and no annotations, and the description is minimal. While 'Not for direct agent use' is a key context, the description lacks details about return values, invocation patterns, or how it relates to the broader workflow. This is insufficient for an agent to understand the tool beyond avoiding it.

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

Parameters3/5

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

The schema description coverage is 100%, so the parameters are already well documented. The description adds no additional parameter semantics, making a baseline score of 3 appropriate.

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

Purpose5/5

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

The description explicitly states what the tool does (refreshes upload/parse/render status, page images, and extracted blocks) and identifies it as an internal viewer widget. This is a specific verb+resource combination and clearly distinguishes it from sibling tools like view_document by labeling it as internal.

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

Usage Guidelines4/5

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

The description provides a clear exclusion: 'Not for direct agent use.' This tells the agent when not to use it, which is valuable guidance. However, it does not explicitly name alternatives like poll_view_commands, so it falls short of a 5.

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