Skip to main content
Glama
Sign In
Open Library MCP Server

Open Library MCP Server

by jay1234624
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_book_ratings

Retrieves the average rating and star count distribution for a book work using its ID.

Instructions

Get aggregate reader ratings for a book work (average score and star counts)

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

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

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral traits. It only states what the tool returns (aggregate ratings), but does not disclose any side effects, caching behavior, or limitations. The read-only nature is implied but not explicit.

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, well-structured sentence with no wasted words. It is front-loaded with the core purpose and immediately informative.

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?

Given the tool's simplicity (one parameter, clear return type described), the description is nearly complete. It specifies 'average score and star counts', leaving little ambiguity, though no output schema exists. It could mention the format of the output but is sufficient for most use cases.

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 100% for the single parameter 'workId', with a clear description. The tool description adds no extra 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 tool's purpose: retrieving aggregate reader ratings (average score and star counts) for a book work. This verb+resource combination is specific and distinguishes it from siblings like 'get_work_details' or 'get_book_summary', which serve different functions.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or context for selection among similar tools like 'get_work_details' or 'get_book_details_by_isbn'.

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