Skip to main content
Glama

get_document

Read-onlyIdempotent

Retrieve metadata and reading details for a single Kavita book by series ID, including author, summary, collections, progress, file path, and Kavita link—not book content.

Instructions

Details of one book: author, summary, collections, word count, pages, reading progress, added date, file path, want-to-read, Kavita link. Never the content.

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": {
      "series_id": "<series_id>"
    },
    "name": "get_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
series_idYesKavita series ID (from list_library, search or add_document)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/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 genuine value with the negative constraint 'Never the content,' which sets retrieval expectations, but says nothing about error behavior for missing or unauthorized series.

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?

A single dense sentence, front-loaded with the core purpose, followed by the payload list and a scope negator. Every clause carries information, and no output schema exists that would make the field list redundant.

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?

With no output schema, the description does the work of describing the return surface field by field, and annotations handle safety. It is nearly complete for a simple one-parameter lookup; only failure modes and pagination/size concerns are unaddressed.

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?

One parameter with 100% schema coverage, so the schema already explains series_id and its provenance. The description adds no meaning about the parameter, so the baseline 3 applies.

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 ('Details of one book') and enumerates exactly what is returned, plus an explicit scope boundary ('Never the content'). It does not name any sibling, so an agent must still infer from names like update_document that this is the read path.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance appears in the description. The only discovery hint ('from list_library, search or add_document') lives in the schema's series_id field, not the description, and nothing tells the agent how this differs from reading_status or want_to_read queries.

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