ppt-generator

Overview Schema Source Related Servers Discussions Admin

prepare_review

Generate a structured design-rule review prompt and response schema for a single slide. Initiate parallel reviews by preparing review tasks with project ID and slide index.

Instructions

Prepares a design-rule review task for ONE slide (mechanical lint baked in as a hint).

No LLM call. Returns the review prompt + response_schema. Generate the review JSON, then call ingest_review. Review slides in parallel.

Args: project_id: Target project ID (required). slide_index: 1-based slide position.

Returns: JSON with system_prompt, user_prompt, response_schema, project_id, slide_index.

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": {
      "project_id": "<project_id>",
      "slide_index": "<slide_index>"
    },
    "name": "prepare_review"
  }
}

Input Schema

Name	Required	Description	Default
`project_id`	Yes
`slide_index`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Jul 10, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Discloses that no LLM call is made and describes the return format (review prompt + response_schema). Without annotations, this is helpful but could mention mutability or side effects. The description is straightforward about its non-destructive nature.

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?

Highly concise with two well-structured paragraphs covering purpose, usage, arguments, and return. Uses formatting (bold, bullet-like) to highlight key points. Every sentence adds value without redundancy.

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?

Given the tool's simplicity (2 required params, clear output schema), the description covers all essential aspects: purpose, output format, workflow integration (call ingest_review), and parallelization hint. No gaps are apparent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds crucial details: project_id as 'Target project ID' and slide_index as '1-based slide position'. Since schema had 0% description coverage, this fully clarifies the parameters' meaning and usage.

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?

The description explicitly states it prepares a design-rule review for ONE slide, distinguishes it from other 'prepare_*' siblings by specifying the review focus and mentioning mechanical lint. It also directs to call ingest_review, clarifying its role in the workflow.

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?

Provides clear instructions: generate review JSON then call ingest_review, and suggests reviewing slides in parallel. Does not explicitly state when not to use or compare to alternatives, but the context implies it's the only tool for this task.

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