Skip to main content
Glama

Estimate the wait for a title

estimate_wait
Read-onlyIdempotent

Estimate how long you would wait if you placed a hold today, using the live hold queue, copy counts, and due dates, and see other formats with shorter waits.

Instructions

Estimate how long you would wait if you placed a hold today, from the live hold queue, copy count and due dates. Also lists other formats of the same work with a shorter queue. This is an estimate computed by Stacks, not a figure published by the library.

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": "estimate_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
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".
loan_daysNoThe library's loan period in days. 21 is typical for books.

Output Schema

NameRequiredDescriptionDefault
basisYesHow the estimate was computed.
holdsYes
titleYes
formatYes
sourceYesProvenance of the data.
libraryYes
title_idYes
on_shelf_atYesUp to 8 branches with a copy on the shelf.
available_nowYesTrue if a copy is on a shelf somewhere right now.
circulating_copiesYes
estimated_wait_daysYesNull when no estimate is possible (e.g. no circulating copies).
faster_alternativesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world behavior, so the bar is lower. The description still adds real value by disclosing the data sources behind the computation and, importantly, that the figure is a Stacks-computed estimate rather than a library-published number, which tells the agent how to caveat the result.

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 tight sentences, front-loaded with the core estimate and its inputs, followed by the secondary output and the provenance caveat. No filler; the middle sentence about other formats is slightly compressed but still readable.

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?

An output schema exists, so return structure need not be spelled out, and the description still signals that alternative formats are part of the response. For a read-only, single-title estimation tool this is essentially complete, missing only cross-tool routing guidance.

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 library, title_id and loan_days are all documented in the schema itself. The description adds nothing about how loan_days changes the estimate or where library ids come from, so it sits at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource: estimating hold wait time from the live hold queue, copy count and due dates, plus a secondary output of faster formats. This clearly distinguishes it from check_availability and get_title in substance, though it never names a sibling explicitly.

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?

'If you placed a hold today' frames the scenario but does not state when to prefer this over check_availability or get_title, nor any exclusions or prerequisites. Usage is implied rather than prescribed.

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