Skip to main content
Glama

Watch a title for availability

watch_title

Monitor a library title on a schedule and send notifications when its availability changes, such as a copy returning to the shelf.

Instructions

Create a standing watch on a title using TinyFish Monitor. TinyFish re-reads the title's page on a schedule and detects when its availability changes (for example a copy comes back on the shelf). Notifications go to the webhook you pass, or to the alerts set up in the TinyFish dashboard. Use list_watches to see watches and their current availability.

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

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.
check_everyNoHow often TinyFish re-checks the page.6_hours
webhook_urlNoOptional public HTTPS endpoint TinyFish calls when the page changes.

Output Schema

NameRequiredDescriptionDefault
watchYes
sourceYesProvenance of the data.
already_existedYesTrue if this title was already being watched; the existing watch is returned and nothing new is created.
availability_at_creationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4/5.0
Behavior3/5

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

Annotations already disclose openWorldHint=true, idempotentHint=false, readOnlyHint=false, so the agent knows this is a mutating, externally reaching operation. The description adds useful behavior beyond that — scheduled re-checks, detection of availability changes, and webhook-vs-dashboard delivery. It remains silent on duplicate-watch behavior (important given idempotentHint=false) and on how a watch is later removed.

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?

Three tight sentences, front-loaded with the action, then mechanism, then notification routing, then the follow-up tool. No redundant restatement of the name or schema fields.

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?

For a mutating, open-world tool with an output schema (so return values need not be described), the description covers what is created, how it behaves over time, and where notifications land. The gaps are duplicate-watch semantics and how to stop a watch, both of which an agent managing lifecycle would want.

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%, so title_id, library, check_every, and webhook_url are already documented. The description adds one genuinely new semantic: if no webhook is supplied, notifications fall back to dashboard alerts, which clarifies the optionality of webhook_url. Beyond that it defers to the schema, matching the baseline.

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: "Create a standing watch on a title using TinyFish Monitor", and immediately explains what a watch is (periodic re-read with change detection). The scope is distinguishable from list_watches and cancel_watch without opening any schema.

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?

Gives clear context for use (you want to be notified when availability changes) and points to list_watches for follow-up inspection. It does not explicitly contrast with check_availability (one-shot vs standing) or note that cancel_watch ends a watch, so the when-not branch is left implicit.

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