Skip to main content
Glama
NoEdgeAI

Doc2x MCP Server

by NoEdgeAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

doc2x_convert_export_wait

Wait for an export job to finish. Prefer calling doc2x_convert_export_submit first, then wait with uid+to. For backward compatibility, if formula_mode is provided and this job was not submitted in-process, this tool will submit once then…

Instructions

Wait for an export job to finish. Prefer calling doc2x_convert_export_submit first, then wait with uid+to. For backward compatibility, if formula_mode is provided and this job was not submitted in-process, this tool will submit once then wait.

Input Schema

NameRequiredDescriptionDefault
toYesExpected target format. Rejects contradictory legacy URL format hints; current download URLs may use opaque object IDs. Keep exports for the same uid sequential.
uidYesDoc2x parse task uid returned by doc2x_parse_pdf_submit.
filenameNo
max_wait_msNo
formula_modeNo
filename_modeNoFor auto-submission: 'auto' strips the target extension and shortens names to at most 50 Unicode characters with a stable hash suffix; 'raw' preserves the basename and rejects longer names.
formula_levelNoOptional formula degradation level used when this tool auto-submits export (formula_mode must be provided). Effective only when source parse uses model=v3-2026 (ignored by v2).
poll_interval_msNo
merge_cross_page_formsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.7
    • addedInput schema / properties / filename / minLength
      Added value: +1
    • addedInput schema / properties / filename_mode / description
      Added value: +"For auto-submission: 'auto' strips the target extension and shortens names to at most 50 Unicode characters with a stable hash suffix; 'raw' preserves the basename and rejects longer names."
    • addedInput schema / properties / formula_level
      Added value: +{
+  "anyOf": [
+    {
+      "const": 0,
+      "type": "number"
+    },
+    {
+      "const": 1,
+      "type": "number"
+    },
+    {
+      "const": 2,
+      "type": "number"
+    }
+  ],
+  "description": "Optional formula degradation level used when this tool auto-submits export (formula_mode must be provided). Effective only when source parse uses model=v3-2026 (ignored by v2)."
+}
    • changedInput schema / properties / to / description
      Previous value: -"Expected target format. Used to verify the result URL."New value: +"Expected target format. Rejects contradictory legacy URL format hints; current download URLs may use opaque object IDs. Keep exports for the same uid sequential."
  2. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose a critical hidden side effect: this 'wait' tool can silently perform a write (submit an export job) when formula_mode is supplied and the job wasn't submitted in-process. That is genuinely valuable. However it says nothing about timeout semantics, whether max_wait_ms expiry raises or returns partial state, or whether waiting blocks/polls server-side.

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?

Three short sentences, front-loaded with the primary action, followed by the preferred workflow, then the legacy exception. Nothing is padded, though the backward-compatibility sentence is dense enough that it could be parsed as covering the main path.

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

Completeness3/5

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

For a 9-parameter polling/wait tool with no annotations and no output schema, the description explains the happy path and the legacy path but omits what a completed wait yields and what happens on timeout or failure. An agent can start the call but cannot fully predict its outcome or its error behavior.

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?

Schema coverage is only 44% across 9 parameters, so the description must compensate and only partially does: it names uid and to as the wait keys and ties formula_mode to the auto-submit trigger. The other six parameters (max_wait_ms, poll_interval_ms, filename, merge_cross_page_forms, filename_mode) get no treatment in the description, and formula_level is only inferable via the schema's own note that formula_mode must be provided.

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+resource: 'Wait for an export job to finish', and names the prerequisite sibling doc2x_convert_export_submit. It does not differentiate itself from doc2x_convert_export_result, which is the obvious other half of the flow, leaving some ambiguity about which call actually returns the artifact.

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?

'Prefer calling doc2x_convert_export_submit first, then wait with uid+to' gives an explicit ordering and the required arguments. The backward-compatibility path (formula_mode present + job not submitted in-process → auto-submit once) explains a second legitimate usage mode. No 'when not to use' guidance, e.g. that an already-finished job should go straight to the result 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