Skip to main content
Glama

Search the catalogue

search_catalog
Read-onlyIdempotent

Search a public library’s catalog by title, author, subject, or keyword to find books, eBooks, audiobooks, DVDs, and more with live availability and hold queues.

Instructions

Search a library's catalogue for books, eBooks, audiobooks, DVDs and more. Returns typed titles with live availability counts and hold queues. Use the title_id of a result with check_availability to see which branches have a copy on the shelf.

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": {
      "query": "<query>"
    },
    "name": "search_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResults page. A page holds 20 titles at most libraries and 10 at some; `pages` gives the count.
queryYesWhat to search for: a title, author, subject or keywords. At most 200 characters.
formatNoOnly this format: book, ebook, audiobook, eaudiobook, large_print, graphic_novel, picture_book, dvd, bluray, music_cd, magazine (or a platform format code such as BK).
libraryNoLibrary system id such as "tpl" (Toronto), "vpl" (Vancouver), "chipublib" (Chicago). Get it from find_library. A city or library name also works.
search_typeNokeyword
available_at_branchNoOnly titles with a copy available right now at this branch (name or code from list_branches).

Output Schema

NameRequiredDescriptionDefault
pageYes
pagesYes
queryYes
totalYesTotal matching titles across all pages.
sourceYesProvenance of the data.
libraryYes
resultsYes
did_you_meanYesThe site's spelling suggestion, if it had one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds genuinely useful behaviour beyond that: results carry live availability counts and hold queues, and title_id is the join key to check_availability. It says nothing about result limits per page, empty-result behaviour, or response ordering, so it adds some but not rich context.

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?

Three sentences, front-loaded with purpose, then return shape, then the follow-up hook. Every sentence earns its place and nothing is padded, though the middle sentence could be trimmed slightly.

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?

With an output schema present and rich annotations, the description need not explain return values in detail, and it doesn't. What it covers is sufficient to call the tool correctly; only pagination and library-scoping defaults are left entirely to the schema, which is acceptable.

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 83%, so the schema already documents query, format, library, page and available_at_branch with examples and enum-like value lists. The description adds no parameter-level meaning beyond what the schema provides, so the baseline 3 applies.

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 opens with a specific verb-plus-resource ("Search a library's catalogue") and enumerates the material types covered (books, eBooks, audiobooks, DVDs). It also describes the return shape (typed titles with availability counts and hold queues), which separates it cleanly from siblings like get_title or check_availability.

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?

It gives an explicit follow-up path: take the title_id from a result and call check_availability to see which branches hold a copy. That is clear context for the search-then-verify workflow, but it does not state when to prefer get_title or ask_library over a keyword search, or when a search is unnecessary.

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