kadal-deck

Official

by kadalcc

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Move a slide

slide_move

Idempotent

Moves a slide to a specified index to reorder deck content; set vertical to stack it beneath the slide before its new position.

Instructions

Move a slide so it ends up at index to; vertical stacks it beneath the slide before its new place.

Input Schema

Name	Required	Description
`to`	Yes	The index the slide will have after the move.
`dir`	No	Deck folder (contains deck.mdx). Absolute, or relative to the server's folder. Default: the server's folder.
`slide`	Yes	A slide: 0-based index (authored order, as deck_outline lists them), "h.v", or its id.
`vertical`	No

Output Schema

Name	Required	Description	Default
`ok`	Yes
`deck`	Yes
`files`	Yes
`notes`	Yes
`slide`	Yes
`action`	Yes
`slides`	Yes
`diagnostics`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.6Oct 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare that this is a mutating, non-destructive, idempotent operation. The description adds some context about the final index and vertical stacking behavior, but it does not explain how other slides are reindexed or what happens with invalid indices. The vertical clause is also somewhat ambiguous.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single compact sentence and is front-loaded with the core operation. However, the vertical-stacking clause is phrased in a way that is slightly hard to parse.

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

Completeness3/5

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

With annotations and an output schema present, the description covers the core operation. It still omits important behavioral details for a move operation, such as index shifting for other slides or invalid-index handling.

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 75%, with clear descriptions for slide, to, and dir. The description adds the only meaningful missing semantics for 'vertical', but it does so ambiguously and does not add further detail for the other parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Move a slide') and clarifies the target index semantics. It clearly distinguishes this from siblings like slide_add, slide_update, and slide_remove, though it does not name those alternatives explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the operation: use this to reposition an existing slide. There is no explicit guidance on when to prefer this over slide_update or other siblings, nor any exclusions or prerequisites.

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