Skip to main content
Glama
Sign In

AI Agent Shelter

by io.github.NeuralDEEPnet
OverviewDiscussionsAdmin

office-powerpoint-mcp__add_slide

[Office PowerPoint MCP] Add a slide to a PowerPoint presentation using a structured layout template.

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": {
      "presentation_id": "<presentation_id>",
      "title": "<title>"
    },
    "name": "office-powerpoint-mcp__add_slide"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoOptional speaker notes
titleYesSlide headline
layoutNoSlide layout template: title_slide, chapter_intro, two_column_text, key_metrics_dashboard, timeline_slide, or thank_you_slide
bulletsNoBullet points or key takeaways for the slide
presentation_idYesTarget .pptx presentation identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it doesn't say where the slide is inserted (append vs. position), what happens on an invalid presentation_id, or that repeated calls create duplicate slides despite the non-idempotent hint.

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?

A single front-loaded sentence with no wasted clauses. The "[Office PowerPoint MCP]" prefix is mild noise, but the core statement arrives immediately.

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 5 parameters, full schema coverage and no output schema, the description is minimally adequate but thin for a mutation tool: it doesn't state what is returned (slide index/id) or how the created slide relates to existing ones. An agent could call it, but would be guessing at insertion behavior and result 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 description coverage is 100%, so all five parameters including the layout enum-like list are already documented in the schema. The description only echoes "layout template" and contributes no additional meaning about how layout interacts with title/bullets or about optional notes.

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 ("Add a slide to a PowerPoint presentation") plus the mechanism ("structured layout template"), which is enough to distinguish it from create_presentation or get_presentation_summary. It stops short of naming a sibling or clarifying how it relates to apply_professional_design or manage_text.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named. The phrase "using a structured layout template" only faintly implies the intended scenario, and nothing states the prerequisite that a valid presentation_id must already exist.

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

All AI Agent Shelter toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources