Skip to main content
Glama

Bookbrainz

by io.github.pipeworx-io

Search

search
Read-onlyIdempotent

Search BookBrainz (MetaBrainz open book database) for works, editions, authors, publishers, series, or edition-groups by free-text query. Returns matching entity records with their BookBrainz UUIDs (bbids) for use with lookup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYeswork | edition | author | publisher | series | edition-group
limitNo1-50 (default 10)
queryYesFree-text query
offsetNo0-based offset

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoTotal number of results matching the query
offsetNoOffset used in the query
entitiesNoArray of matching entities

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive traits. The description adds domain-specific context (BookBrainz database, returns BBIDs) and the tool's purpose, which complements annotations without contradiction.

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?

Two sentences, each serving a distinct purpose: defining the action and resource, then describing the result and its use. No redundant information, highly efficient.

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

Completeness5/5

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

Given the presence of an output schema and comprehensive annotations, the description sufficiently covers what the tool does and the nature of its return. The addition of 'BBIDs for use with lookup' provides useful context.

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 each parameter already described (type, limit, query, offset). The description does not add additional meaning beyond the schema, so baseline score of 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 searches BookBrainz for specific entity types (works, editions, etc.) using free-text queries and returns matching records with BBIDs for lookup. It uses a specific verb and resource, and distinguishes from sibling tools like lookup and search_within.

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?

The description implies the result is for use with lookup but does not explicitly state when to use search versus siblings like 'search_within' or 'resolve_entity'. No when-not or alternative guidance is provided.

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

All Bookbrainz toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation2/5

The tool set mixes three distinct domains: BookBrainz entity access (browse, lookup, search), Pipeworx data routing (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, suggest_questions), and Polymarket betting analysis. Multiple tools have overlapping purposes, particularly the ask_pipeworx variants and the various polymarket_* tools, which an agent could easily confuse.

Naming Consistency4/5

All tool names follow a readable snake_case convention. While some are single verbs (browse, lookup, search), others use compound patterns (ask_pipeworx_grounded, polymarket_edge_tracker, pipeworx_trending), and there are a few noun-first names (entity_profile, pipeworx_feedback, recent_changes). The inconsistency is minor and does not hinder readability.

Tool Count2/5

With 34 tools, this is a large surface for a server named Bookbrainz, yet only 3 tools (browse, lookup, search) actually serve that domain. The remaining 31 tools are unrelated Pipeworx/Polymarket functionality, making the tool count inappropriate for the stated server purpose and suggesting a mislabeled or overloaded server.

Completeness2/5

The BookBrainz domain is severely incomplete: it offers read-only access (search, browse, lookup) but no create, update, or delete operations for entities. For the broader Pipeworx/Polymarket functionality, coverage is quite deep, but that is not the server's stated domain. This leaves a fundamental gap for the BookBrainz use case.

Resources