Storyblok MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it's a retrieval operation via an API, implying read-only behavior, but doesn't specify authentication requirements, rate limits, error conditions, or what happens if the branch ID doesn't exist. This leaves significant gaps for a tool that interacts with an external API.

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 efficiently structured with a clear main sentence followed by a bullet point for the parameter. There's no wasted text, and information is front-loaded appropriately for quick understanding.

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 no annotations, no output schema, and low schema coverage, the description adequately covers the basic purpose and parameter. However, it lacks details on behavioral aspects like authentication, error handling, or return format, which are important for API-based tools. It's minimally viable but has clear gaps.

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 0%, but the description explicitly documents the single parameter 'branch_id' as 'Numeric ID of the branch to retrieve,' which fully compensates for the lack of schema descriptions. This provides clear semantic meaning beyond the schema's type and title.

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 the verb ('Retrieves') and resource ('a single branch (pipeline)'), and specifies it's done via the Storyblok Management API. However, it doesn't explicitly differentiate from sibling tools like 'retrieve_multiple_branches' or 'get_story', though the 'single' vs 'multiple' distinction is implied.

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?

No guidance is provided on when to use this tool versus alternatives like 'retrieve_multiple_branches' for listing branches or 'get_story' for story data. The description lacks context about prerequisites, such as needing branch ID availability, or when this retrieval is appropriate.

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