Skip to main content
Glama
Audiobookshelf MCP Server

Audiobookshelf MCP Server

Check which books are already owned

abs_check_owned
Read-onlyIdempotent

Checks candidate books against your audiobook library to confirm ownership and listening status, so you can filter recommendations before requesting downloads.

Instructions

Given candidate books (title + optional author), report which are already in the library and whether the user has listened to them. Tolerates subtitles, leading articles, punctuation and "(Unabridged)". confidence: exact | likely | possible. Use to filter recommendations before requesting downloads.

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": {
      "books": "<books>"
    },
    "name": "abs_check_owned"
  }
}

Input Schema

NameRequiredDescriptionDefault
booksYes
libraryNoLibrary ID or name. Default: search every allowed book library.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still earns credit by disclosing fuzzy-match behavior (subtitles, leading articles, punctuation, '(Unabridged)') and a three-level confidence scale, which materially changes how an agent should interpret results. It omits latency/rate considerations for batch sizes up to 50, which keeps it off a 5.

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 input shape and the output shape, then matching behavior, then the use case. The telegraphic 'confidence: exact | likely | possible' is dense but precise, and nothing is padding.

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?

There is no output schema, so the description must carry return semantics, and it does: ownership plus listened status plus a confidence enum. Matching tolerance and the library-scoping default are also covered. What's missing is how partial matches at the 'possible' confidence should be treated, which matters for a filter-before-download workflow.

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 50%: the 'library' parameter is documented in-schema, and the description covers 'books' items as title plus optional author, so the structural gap is largely filled. It adds no detail on batching, per-item tolerance scope, or how the default 'search every allowed book library' affects result interpretation beyond the schema text. Baseline 3 is right when the schema carries the load.

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: given candidate books, report which are already owned and whether they've been listened to. That reads as a bulk ownership-lookup, clearly distinct from a discovery sibling like abs_search_library, so an agent can route between them without opening either 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?

Provides concrete usage context: 'Use to filter recommendations before requesting downloads.' That tells the agent this is a pre-download dedupe step. It stops short of an explicit when-not or a named alternative, but the positional guidance is clear.

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