Dokyumi Document Extraction

Download saved extraction data

dokyumi_export_extractions

Read-onlyIdempotent

Get a browser-authenticated CSV or XLSX download for 1–50 selected completed or review-needed results. Includes values, confidence, validation and review links. Open while signed into the same Dokyumi account. Source data remains unverified.

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": {
      "extraction_ids": "<extraction_ids>",
      "format": "<format>"
    },
    "name": "dokyumi_export_extractions"
  }
}

Input Schema

Name	Required	Description	Default
`format`	Yes
`extraction_ids`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes
`status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 21, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive. The description adds valuable context beyond them: browser-authenticated download, session/same-account requirement, result-state eligibility, and the caveat that source data remains unverified.

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 compact sentences, front-loaded with the core action and format. Each sentence adds a constraint or caveat; slightly telegraphic but efficient.

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

Completeness4/5

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

Covers the essentials: output format, count limits, eligible states, auth requirement, and data-quality caveat; an output schema exists so return details are exempt. Minor missing detail: no explicit mention of enum values or error behavior for ineligible IDs.

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 description coverage is 0%, so the description carries extra burden, but it only indirectly conveys the 1–50 limit and completed/review-needed constraint. It does not name the format enum values or clarify that extraction_ids are UUIDs, leaving gaps the schema partially implies (maxItems/minItems, enum).

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?

States a specific verb (export/download) and resource (extraction data) plus formats CSV/XLSX. Distinguishes it from siblings like dokyumi_get_extraction by emphasizing download output and bulk selection.

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?

Constrains usage: 1–50 selected results that are completed or review-needed, and warns to open while signed into the same account. Lacks explicit when-not-to-use guidance and doesn't name alternatives like dokyumi_get_extraction for single results.

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

All Dokyumi Document Extraction tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?