get_authorAuthor profile + their audiobook works. Returns biography, photo, country, and the full list of audiobook editions where this person is credited as author / co-author / editor.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Author slug (lowercase, hyphenated). Discoverable via search_audiobooks results. Example: "stephen-king". |
| Name | Required | Description | Default |
|---|---|---|---|
| value | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / slug / descriptionAdded value: +"Author slug (lowercase, hyphenated). Discoverable via search_audiobooks results. Example: \"stephen-king\"."Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "value": {
+ "anyOf": [
+ {
+ "additionalProperties": false,
+ "properties": {
+ "bio": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "name": {
+ "type": "string"
+ },
+ "photo_url": {
+ "anyOf": [
+ {
+ "format": "uri",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "slug": {
+ "maxLength": 120,
+ "minLength": 1,
+ "pattern": "^[a-z0-9]+(-[a-z0-9]+)*$",
+ "type": "string"
+ },
+ "url": {
+ "$ref": "#/properties/value/anyOf/0/properties/works/items/properties/url"
+ },
+ "works": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "author": {
+ "additionalProperties": false,
+ "properties": {
+ "name": {
+ "type": "string"
+ },
+ "slug": {
+ "$ref": "#/properties/value/anyOf/0/properties/slug"
+ }
+ },
+ "required": [
+ "slug",
+ "name"
+ ],
+ "type": "object"
+ },
+ "cover_url": {
+ "anyOf": [
+ {
+ "format": "uri",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "lowest_price_czk": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "partner_count": {
+ "minimum": 0,
+ "type": "integer"
+ },
+ "slug": {
+ "$ref": "#/properties/value/anyOf/0/properties/slug"
+ },
+ "title": {
+ "type": "string"
+ },
+ "url": {
+ "format": "uri",
+ "pattern": "^https\\:\\/\\/audioknihy\\.cz\\/",
+ "type": "string"
+ }
+ },
+ "required": [
+ "slug",
+ "title",
+ "author",
+ "cover_url",
+ "lowest_price_czk",
+ "partner_count",
+ "url"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "slug",
+ "name",
+ "bio",
+ "photo_url",
+ "works",
+ "url"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "required": [
+ "value"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value by specifying what is returned (biography, photo, country, full list of audiobook editions), which is beyond the annotations. 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the core purpose, then expanding on details. Every sentence adds value: first sentence states what it returns, second sentence lists fields. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the presence of an output schema (not shown but indicated), the description adequately covers return fields and parameter semantics. It does not mention that the slug is required or that it uniquely identifies an author, but the schema handles that. Overall, it is complete for this tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% (slug parameter has a description). The description adds context: slug is discoverable via search_audiobooks and includes an example ('stephen-king'). This adds meaning beyond the schema's pattern constraint, justifying a score above baseline 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that the tool returns an author profile along with their audiobook works, listing specific fields (biography, photo, country) and the full list of audiobook editions. It distinguishes this tool from siblings like get_narrator and search_audiobooks by specifying the scope (author profile + works).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implicitly indicates when to use: when you need an author's profile and their works. It does not explicitly state when not to use or provide alternatives, but the sibling list (e.g., search_audiobooks, get_narrator) helps differentiate. The context is clear but lacks explicit exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.