Dokyumi Document Extraction

Find document workflow starters

dokyumi_list_starters

Read-onlyIdempotent

Find and preview a ready-made document schema by use case or category. Includes fields, review checks and explicitly synthetic examples. No upload or credit use.

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_list_starters"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	No
`offset`	No
`category`	No

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 21, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds value beyond them by noting 'No upload or credit use' and that examples are 'explicitly synthetic', which tells the agent the data is safe to preview and costs nothing.

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?

Three tight sentences, front-loaded with the core action and resource, then return contents, then the no-cost/no-upload caveat. Every sentence adds information.

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?

An output schema and rich annotations exist, so the description needn't explain return values; it still helpfully previews fields, review checks, and synthetic examples. The remaining gap is pagination behavior for limit/offset and differentiation from dokyumi_list_schemas.

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 partially does by mapping 'use case' to query and 'category' to the category enum. It says nothing about limit, offset, or pagination, leaving half the parameters undocumented.

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 ('Find and preview') and resource ('ready-made document schema'), scoped by use case or category. A sibling named dokyumi_list_schemas exists, and the description doesn't clarify how starters differ from schemas, so sibling differentiation is incomplete.

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

Usage Guidelines3/5

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

The phrase 'by use case or category' implies the lookup is for discovering a template, but there is no explicit when-to-use guidance or named alternative such as dokyumi_list_schemas. Usage is inferable rather than stated.

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?