Skip to main content
Glama

Gutendex Get Book

gutendex_get_book
Read-onlyIdempotent

Get full details for a book by ID. Returns title, author, publication year, language, available formats, and download count.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": 1342
    },
    "name": "gutendex_get_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe numeric Project Gutenberg book ID.

Output Schema

NameRequiredDescriptionDefault
idYesProject Gutenberg book ID
titleYesBook title
authorsYesList of book authors
formatsYesAvailable download formats and URLs
subjectsYesSubject tags for the book
languagesYesLanguages the book is available in
download_countYesNumber of downloads

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description's second sentence enumerates returned fields, but an output schema exists, so that adds little; nothing is said about error behavior for a missing ID, rate limits, or response size.

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?

Two short sentences with the action front-loaded and no filler. The field enumeration is slightly redundant against the output schema but serves as a quick scan of what comes back.

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?

For a one-parameter read tool with full schema coverage, rich annotations, and an output schema, the description covers the essentials. The only meaningful gap is failure behaviour for an invalid or nonexistent book ID.

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 coverage is 100% and the single parameter is already documented as "The numeric Project Gutenberg book ID." The description's phrase "by ID" adds no syntax, range, or format detail beyond the schema, 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?

"Get full details for a book by ID" pairs a specific verb with a specific resource and keys the lookup to an ID, which implicitly contrasts with the sibling search tool. It stops short of naming gutendex_search_books as the alternative, so the differentiation is inferable rather than stated.

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?

Usage is only implied: an agent must already have a numeric ID to call this, so it follows a search or a prior result. There is no explicit when-to-use or when-not-to-use guidance and no mention of what to do if the ID is unknown.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.