Skip to main content
Glama
Sign In
Open Library MCP Server

Open Library MCP Server

by jay1234624
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_subject_insights

Discover books and trends for any subject on Open Library. Specify subject name with optional pagination to explore relevant works.

Instructions

Get books and trends for a subject/topic on Open Library (e.g. science_fiction)

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": {
      "subject": "<subject>"
    },
    "name": "get_subject_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results to return (default 20, max 100)
offsetNoStarting offset for pagination (default 0)
subjectYesSubject name, e.g. 'science fiction' or 'science_fiction'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

Without annotations, the description must disclose behavior. It mentions 'get' implying read-only, but does not confirm whether results are paginated, sorted, or if any side effects occur. The parameters limit/offset hint at pagination, but this is not stated.

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?

Single sentence that is front-loaded and contains no filler. Every word is essential, making it highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is too brief given the absence of an output schema and annotations. It does not explain what 'trends' means, how pagination works, or the structure of returns. More detail is needed for an AI to use it effectively.

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% with clear parameter descriptions. The description adds only the subject example, providing minimal extra value beyond the schema. 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 retrieves books and trends for a subject/topic on Open Library, with a specific example ('science_fiction'). This differentiates it from siblings like search_books which likely handle general queries.

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 explicit guidance on when to use this tool versus alternatives such as search_books or get_book_summary. The context of subject/topic is implied but not contrasted with other search functions.

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