Dokyumi Document Extraction

Check processing access and document limits

dokyumi_preflight_extraction

Read-onlyIdempotent

Read current processing access, page and schema limits, and optionally check a saved schema. BYOK workspaces have no monthly extraction cap and pay OpenRouter separately; subscription workspaces use existing credits. Does not upload, reserve credits, or start extraction. Actual pages and balance are rechecked on extraction.

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": "dokyumi_preflight_extraction"
  }
}

Input Schema

Name	Required	Description	Default
`pages`	No
`schema_slug`	No

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 21, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the read-only annotations, the description explains the billing model distinction between BYOK and subscription workspaces, clarifies that no credits are reserved, and notes that actual pages and balance are rechecked during extraction. This is meaningful behavioral context an agent could not get from annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four tight sentences, front-loaded with what the tool reads. Each sentence adds distinct value: scope, billing context, side-effect exclusions, and recheck behavior.

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?

The output schema exists, so return values need not be explained, and the annotations plus description cover safety and side effects well. The only material gap is that the role of the `pages` input is not fully spelled out despite zero schema-level parameter documentation.

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 must carry parameter meaning. It clearly connects schema_slug to checking a saved schema, and it implies that pages relates to page limits, but it never explicitly states that `pages` is the requested page count to validate against the limit.

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 states a specific read operation: current processing access, page and schema limits, plus optional saved-schema checking. It distinguishes itself from extraction siblings by explicitly saying it does not upload, reserve credits, or start extraction.

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 preflight framing and the statement that it does not start extraction make the intended usage clear: check access/limits before a real extraction. It does not explicitly name dokyumi_extract_document as the alternative, but the context is strong enough for an agent to infer the routing.

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?