Skip to main content
Glama

Check availability by branch

check_availability
Read-onlyIdempotent

Find live copy-level availability for a title by title ID: see which branches have it on the shelf now, call numbers, and due dates for checked-out copies.

Instructions

Live, copy-level availability for one title: which branches have it on the shelf right now, call numbers, and due dates for checked-out copies. Branches with a copy on the shelf are listed first.

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": {
      "title_id": "<title_id>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of branches to return.
branchNoOnly this branch (name or code).
libraryNoLibrary system id such as "tpl" (Toronto), "vpl" (Vancouver), "chipublib" (Chicago). Get it from find_library. A city or library name also works.
title_idYesA title_id from search_catalog, e.g. "S234C3970025".
on_shelf_onlyNoOnly branches where a copy is on the shelf right now.

Output Schema

NameRequiredDescriptionDefault
titleYes
formatYes
sourceYesProvenance of the data.
libraryYes
summaryYes
branchesYes
title_idYes
truncatedYesTrue if more branches matched than `limit`.
branches_holdingYesBranches that own at least one copy.
branches_on_shelfYesBranches with a copy on the shelf right now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open world), so the description's job is lighter; it adds real value by disclosing that results are live/real-time and that branch ordering prioritizes available copies. It does not discuss latency, caching staleness, or behavior when a title has no holdings anywhere.

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?

Two tight sentences, front-loaded with the resource and scope, with the ordering rule placed at the end where it belongs. No filler; slightly more compact framing could have merged the holdings list and ordering into one clause.

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 a 100%-covered schema, an output schema, and full annotations, the description carries little extra burden and covers the essentials (scope, freshness, result ordering). The main residual gap is that the title_id and library-id provenance, which comes from other tools, is only documented in the schema rather than flagged in the description.

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%, so each parameter (title_id, library, branch, limit, on_shelf_only) is already documented in the schema, which sets the baseline at 3. The description only obliquely echoes on_shelf_only via 'on the shelf right now' and adds no format, default, or interaction detail beyond the schema.

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?

States a specific verb and resource ('check availability for one title') and pins down the granularity ('copy-level', 'which branches have it on the shelf right now', call numbers, due dates). This is clearly distinguishable from catalog search or title-detail siblings, which do not report per-branch holdings.

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?

Usage is only implied: an agent can infer this is the tool for 'is it available near me' questions, but there is no explicit when-to-use versus alternatives, no stated prerequisite chain (search_catalog for title_id, find_library for library id), and no when-not-to-use guidance. The sentence about ordering ('on the shelf first') is output behavior, not selection guidance.

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