Skip to main content
Glama
blazar-source

r7-office

by blazar-source
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

r7_slide_create

Create a new PPTX deck or append a slide to an existing one, reusing its layout, master and theme without altering the slides already there.

Instructions

Create a new PPTX deck, or append a slide to an existing one built on one of the deck's own layouts. Appending never modifies the slides already present, and the layout, master and theme the deck already has are reused rather than replaced. Pass baseSlideIndex to clone an existing slide instead of using a layout.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoText for the new slide's title placeholder (or for slide 1 when creating a deck).
filePathYesPath to the PPTX file. A missing file is created as a new deck; an existing one gets a new slide.
subtitleNoText for the subtitle placeholder, when the layout has one.
layoutNameNoLayout name, e.g. "Титульный слайд". Matched exactly first, then as a substring.
layoutTypeNoPowerPoint layout type: title, obj, twoObj, blank, titleOnly, picTx, secHead.
outputPathNoWrite to a copy instead of editing in place.
paragraphsNoBody text, one entry per paragraph. An entry may be a string, or { text, runs?, bullet?, numbered?, alignment?, size?, color? }.
layoutIndexNo0-based layout to build from, as listed by r7_slide_read. Omit for a sensible default ("heading and content").
baseSlideIndexNoClone this existing slide instead of building from a layout.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations the description carries the full burden, and it delivers the key traits: appending is non-destructive, layout/master/theme are reused rather than replaced, and baseSlideIndex clones a slide. It does not touch permissions, return format, or in-place vs copy behavior (left to the outputPath param).

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?

Three sentences, zero waste, front-loaded with the primary purpose and followed by the behavioral and cloning details. Each sentence earns its place.

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?

For a 9-parameter mutation tool with no annotations and no output schema, the description adequately conveys the create/append distinction and non-destructive behavior. Minor gaps (authentication, response expectations) remain, but nothing essential for calling it correctly is missing.

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 description coverage is 100%, so the baseline is 3 and the schema already documents every parameter. The description echoes the baseSlideIndex cloning semantics already stated in the schema, adding only marginal meaning beyond structured data.

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 (create) and resource (PPTX deck/slide), and covers the dual behavior of creating a new deck versus appending a slide to an existing one. It separates itself from siblings like r7_slide_edit and r7_slide_format by making clear appending never modifies existing slides.

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?

Gives clear context: a missing file creates a new deck, an existing one gets a new slide, and baseSlideIndex switches to clone mode. It does not explicitly name an alternative sibling (e.g., r7_slide_edit) or state exclusions, so it stops short of a 5.

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