Skip to main content
Glama

Check deck order

check_deck
Read-onlyIdempotent

Validate the slide ORDER of a whole deck before you build it. check_slots looks at one slide's text; this looks at the sequence. Input: layout_ids, the layout of every slide in order. Returns { slide_count, ok, error_count, warning_count, issues[], unknown_layout_ids? }. Each issue has code, severity ("error" must be fixed, "warning" is a quality note), order (slide number), layout_id, message and a one-line fix. Codes: closer_not_last (a closing layout that is not the last slide), repeated_layout (the same layout on consecutive slides). It does not judge whether slides look alike. ok is true when there are no errors.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "layout_ids": "<layout_ids>"
    },
    "name": "check_deck"
  }
}

Input Schema

NameRequiredDescriptionDefault
layout_idsYesLayout ids in slide order, e.g. from suggest_deck or your own plan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is pre-covered. The description still adds real behavioral context: the full return shape, the error-versus-warning distinction ("error must be fixed"), the meaning of ok, and two named issue codes with their triggers. It stops short of stating whether the deck is mutated, whether checks run against a saved deck or a plan, or how partial failure surfaces, so beyond the annotations it is solid but not exhaustive.

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?

Front-loaded with the purpose and the sibling contrast, then input, then return shape, then issue codes - a logical order for an agent to scan. It is dense, with several parenthetical asides packed into one block, but each sentence carries information the agent would otherwise have to guess at.

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?

One required parameter, fully documented, and no output schema - so the description carries the return contract and does it in detail: slide_count, ok, error_count, warning_count, issues[], unknown_layout_ids?. The issue code list with severities and fix semantics removes the main source of ambiguity for correct interpretation of results.

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%, so layout_ids is already documented with type, min/max items and item type; the baseline is 3. The description restates it as "the layout of every slide in order" and the schema description ties it to suggest_deck or a hand-made plan. That is mild value-add over structured data rather than new semantics, so it sits at 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?

States a specific verb and resource ("Validate the slide ORDER of a whole deck") and immediately distinguishes itself from the sibling check_slots by scope: one slide's text versus the whole sequence. The agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit timing condition ("before you build it") and names the alternative it is not (check_slots). The exclusion is also stated from the other side: "It does not judge whether slides look alike," which tells the agent when this tool is the wrong reach.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources