Skip to main content
Glama

audioknihy.cz Catalog

by cz.audioknihy

Get Publisher Profile

get_publisher
Read-onlyIdempotent

Publisher (nakladatelství) profile + their audiobooks. Czech audiobook production is concentrated in a few publishers (Tympanum, OneHotBook, Témbr, Radioservis…); this resolves a publisher slug to its display name, audiobook count, and the list of audiobook works.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesPublisher slug (lowercase, hyphenated). Example: "tympanum". Discoverable via the /nakladatelstvi index page.
limitNoMaximum number of works to return. 1–50, default 50.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYes

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds domain context (concentration of Czech publishers) and confirms the return type. No contradictions.

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?

Two concise sentences with no wasted words. The first sentence states the purpose, the second provides important domain context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists, parameter count is low, and annotations are complete, the description is fully sufficient for an agent to understand and use the tool correctly.

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% and both parameters (slug, limit) are well-described in the schema. The description does not add significant additional meaning beyond repeating the schema details.

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 clearly states it resolves a publisher slug to display name, audiobook count, and list of works. It distinguishes from sibling tools like get_author and get_narrator by focusing specifically on publishers.

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 provides context about Czech audiobook publishers and states that the tool resolves a publisher slug. It does not explicitly say when not to use it or compare to alternatives, but the connection to sibling tools is clear.

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

All audioknihy.cz Catalog toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation4/5

Most tools have distinct purposes, but `compare_all_offers` and `find_cheapest_offer` overlap in pricing queries. Descriptions clarify the difference (full table vs. cheapest only), so ambiguity is low. Similarly, `search_audiobooks` and `search_by_filters` are distinct in input style.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., `browse_genres`, `get_audiobook`, `search_by_filters`). No mixing of conventions or irregular naming.

Tool Count5/5

13 tools cover browsing, searching, detailed info, price comparison, analytics, and profiles. The number is well-balanced for the catalog's scope—neither sparse nor excessive.

Completeness4/5

The tool set covers key workflows: discovery, search, details, price comparison, trends, rankings, and partner info. Minor gaps like user reviews or advanced filtering (e.g., partner filter in V2) are acceptable for a focused catalog.

Resources