Skip to main content
Glama
Sign In
ppt-generator

ppt-generator

by haandol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ingest_design_slide

Validates, normalizes, saves, renders, and lints a client-generated slide spec, returning slide file and HTML paths plus lint/overflow feedback for presentation assembly.

Instructions

Ingests the client-generated slide spec: validate, normalize, save, render, lint.

Call AFTER prepare_design_slide with the spec JSON you generated.

Args: project_id: Project ID (required). slide_index: 1-based slide number (same as prepare). spec_json: The slide spec JSON generated by the client, matching the schema. generation_context: Opaque token returned by prepare_design_slide. color_theme: Color theme ("dark" or "light").

Returns: JSON with status, slide_file, slide_html_path, optional lint and overflow.

After ingesting ALL slides, call finalize_design_spec once.

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>",
      "spec_json": "<spec_json>",
      "generation_context": "<generation_context>"
    },
    "name": "ingest_design_slide"
  }
}

Input Schema

NameRequiredDescriptionDefault
spec_jsonYes
project_idYes
color_themeNodark
slide_indexYes
generation_contextYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.8.2
    • addedInput schema / properties / generation_context
      Added value: +{
+  "title": "Generation Context",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "project_id",
-  "slide_index",
-  "spec_json"
-]New value: +[
+  "project_id",
+  "slide_index",
+  "spec_json",
+  "generation_context"
+]
  2. First observedv0.7.0

TDQS

A4.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the side effects (save, render, lint) and the return surface, but omits key write semantics: whether re-ingesting the same slide_index overwrites an existing slide, whether the operation is idempotent, and what happens if the generation_context token is stale or missing.

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?

Front-loaded one-line summary, then Args, Returns, and a bolded workflow reminder. Every line carries information; no restatement of the tool name or filler.

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

Completeness4/5

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

Covers workflow position, all parameters, and the mutation pipeline for a five-parameter write tool, and an output schema exists so return detail is a bonus rather than a necessity. The remaining gap is duplicate-ingest behavior, which matters given the fixed slide_index key.

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

Parameters4/5

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

Schema coverage is 0%, but the Args block compensates by explaining all five parameters, adding real meaning beyond the bare types: slide_index is '1-based' and 'same as prepare', generation_context is an 'opaque token returned by prepare_design_slide', and color_theme values are enumerated. Only required-vs-optional is left implicit for parameters other than project_id.

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?

Names a specific verb and resource plus the internal pipeline it runs: 'validate, normalize, save, render, lint'. It also positions itself against siblings, stating it runs after prepare_design_slide and feeds finalize_design_spec, so an agent can place it in the workflow without inspecting other schemas.

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?

Explicit sequencing: 'Call AFTER prepare_design_slide with the spec JSON you generated' and 'After ingesting ALL slides, call finalize_design_spec once.' Both the precondition and the follow-up are named, leaving nothing to inference.

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

Deploy Server

Other Tools