audioknihy.cz Catalog

Find Cheapest Offer

find_cheapest_offer

Read-onlyIdempotent

Lowest-price active offer for an audiobook across all affiliate partners. USP — only Czech site that compares audiobook prices across all major retail partners.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`work_slug`	Yes	Work slug (lowercase, hyphenated). Example: "to".
`author_slug`	Yes	Author slug (lowercase, hyphenated). Example: "stephen-king".

Output Schema

TableJSON Schema

Name	Required	Description	Default
`value`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedJun 2, 2026

addedInput schema / properties / author_slug / description

Added value: +"Author slug (lowercase, hyphenated). Example: \"stephen-king\"."

removedInput schema / properties / work_slug / $ref
```
Removed value: -"#/properties/author_slug"
```

addedInput schema / properties / work_slug / description

Added value: +"Work slug (lowercase, hyphenated). Example: \"to\"."

addedInput schema / properties / work_slug / maxLength
```
Added value: +120
```
addedInput schema / properties / work_slug / minLength
```
Added value: +1
```
addedInput schema / properties / work_slug / pattern
```
Added value: +"^[a-z0-9]+(-[a-z0-9]+)*$"
```
addedInput schema / properties / work_slug / type
```
Added value: +"string"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "value": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "format": {
+              "type": "string"
+            },
+            "last_seen": {
+              "type": "string"
+            },
+            "original_price_czk": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "partner": {
+              "additionalProperties": false,
+              "properties": {
+                "name": {
+                  "type": "string"
+                },
+                "slug": {
+                  "maxLength": 120,
+                  "minLength": 1,
+                  "pattern": "^[a-z0-9]+(-[a-z0-9]+)*$",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "slug",
+                "name"
+              ],
+              "type": "object"
+            },
+            "price_czk": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "url": {
+              "format": "uri",
+              "type": "string"
+            }
+          },
+          "required": [
+            "partner",
+            "price_czk",
+            "original_price_czk",
+            "format",
+            "url",
+            "last_seen"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "value"
+  ],
+  "type": "object"
+}

First observedMay 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already indicate read-only and idempotent. Description adds that it returns only the lowest-price active offer and compares across all partners, providing useful context beyond annotations.

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 delivers the core purpose; the second adds a distinguishing USP.

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?

Complete for a simple lookup tool with full annotations and output schema. Description clearly explains scope and uniqueness.

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% with parameter descriptions. Description does not add semantic details beyond the schema, meeting 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?

Clearly states it finds the lowest-price active offer for an audiobook across all affiliate partners. The USP differentiates it from siblings like compare_all_offers.

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?

Implies use when cheapest offer is desired, but does not explicitly mention when to use alternatives like compare_all_offers for all offers.

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 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?