Skip to main content
Glama
Sign In
Open Library MCP Server

Open Library MCP Server

by jay1234624
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_book_summary

Retrieve a concise summary of a book's metadata using its Open Library work ID.

Instructions

Get a concise summary of a book's metadata from its Open Library work ID

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": {
      "workId": "<workId>"
    },
    "name": "get_book_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
workIdYesWork ID, e.g. 'OL27448W' or '/works/OL27448W'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'concise summary of a book's metadata', which is vague and does not explain what fields are included, response format, or potential errors. For a tool without annotations, this is insufficient.

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 a single, concise sentence that clearly communicates the tool's purpose without any unnecessary words. It earns its place.

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 has only one parameter, no output schema, and 11 siblings, the description is minimally adequate. It tells what the tool does but lacks details on return values or how it differs from similar tools like get_work_details. More context would improve completeness.

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?

The input schema provides 100% coverage with a clear description and example for workId. The tool description does not add any additional meaning beyond the schema, so baseline 3 is appropriate.

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 clearly states the verb 'get' and the resource 'concise summary of a book's metadata' from an Open Library work ID. It is specific and distinct from siblings like get_work_details or get_book_details_by_isbn, which likely provide more comprehensive information.

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 says 'from its Open Library work ID', providing clear context for when to use the tool. However, it does not mention when not to use it or suggest alternative tools for other input types (e.g., ISBN), which would improve guidance.

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

Deploy Server

Other Tools