Skip to main content
Glama
Sign In
Koha MCP Server

Koha MCP Server

by wrecks1997
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

check_availability

Read-only

Check book availability by biblio_id, returning item-level details such as call number, location, and checkout status. See which copies are available or checked out.

Instructions

Check the availability of a specific book by its biblio_id. Returns item-level details including call number, location, and whether each copy is available or checked out.

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

Input Schema

NameRequiredDescriptionDefault
biblio_idYesThe biblio_id from search_books results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds useful context beyond that: it returns item-level details including call number, location, and the circulation status of each copy. It does not contradict the annotations and provides a clear picture of what the read operation yields.

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?

The description is a single, dense sentence that front-loads the purpose and immediately provides the key return summary. Every word earns its place, with no redundant or filler content.

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 simple one-parameter read-only tool, the description adequately covers purpose and return content (item-level call number, location, availability/checkout status). Although there is no output schema and error behavior is not mentioned, the description provides enough for an agent to invoke the tool correctly in typical use.

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% for the single parameter, and the schema already explains that biblio_id comes from search_books results. The tool description only restates 'specific book' and adds no extra parameter semantics, so the schema carries the burden.

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 uses a specific verb ('check') and resource ('a specific book by its biblio_id'), clearly stating the tool's scope. It also lists the return details (call number, location, availability), which distinguishes it from the sibling search_books that finds books rather than checking 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?

The description implies usage after obtaining a biblio_id from search_books, especially through the parameter description ('The biblio_id from search_books results'). However, it does not explicitly state when to use this tool versus search_books or mention alternative/exclusion scenarios, so it stops short of a 5.

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

Deploy Server

Other Tools