mcp-ebook-read

by ArtiPyHeart

Overview Schema Source Related Servers Discussions Admin

Python

Local

document_ingest_list_jobs

Retrieve recent ingest jobs for a document. Use when the latest job ID is lost or to review ingest history.

Instructions

List recent ingest jobs for one document. Use when the latest job_id was lost or the user asks for ingest history.

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": {
      "doc_id": "<doc_id>"
    },
    "name": "document_ingest_list_jobs"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`doc_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.7Jul 13, 2026

TDQS

B3.3/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 full burden. It lacks details about read-only nature, response format, ordering, or pagination. The term 'recent' is undefined, and the default limit of 20 is not mentioned.

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?

Two sentences, front-loaded with purpose and then use cases. Every sentence adds value, no wasted words.

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?

Given the tool is simple and has an output schema, the description is marginally adequate but omits explanation of 'recent' and the limit parameter. It could benefit from clarifying the list contents.

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

Parameters2/5

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

The description does not explain any parameters. Schema coverage is 0%. It implies doc_id is for the document but says nothing about limit or their types/formats.

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?

The description clearly states it lists recent ingest jobs for one document. It distinguishes from siblings like document_ingest and document_ingest_status by focusing on job history, though it doesn't explicitly name alternatives.

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 explicitly mentions two use cases: when the latest job_id was lost or the user asks for ingest history. It provides clear context but does not specify when not to use it or compare with other tools.

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