Skip to main content
Glama
Sign In
ai-slides-mcp

ai-slides-mcp

by vuhai2002
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

styled_deck

Generate a PowerPoint deck that adopts the style and color scheme from a reference image, using provided prompts to create slide content.

Instructions

Generate a deck matching a reference design image's style and colors (content not copied).

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": {
      "ref_image": "<ref_image>",
      "prompts": "<prompts>"
    },
    "name": "styled_deck"
  }
}

Input Schema

NameRequiredDescriptionDefault
ref_imageYes
promptsYes
aspectNo16:9
out_pptxNodeck.pptx
out_dirNoout

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/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 mentions style copying and not content copying but does not disclose potential side effects, output file creation, or required permissions. The tool creates files but this is not stated.

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?

The single-sentence description is concise and front-loaded with the key action, but it lacks structure and fails to earn its place for parameter details.

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

Completeness2/5

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

Given the tool's complexity (5 params, no output schema, no annotations), the description is incomplete. It does not explain parameters, return values, or behavior beyond the basic purpose.

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

Parameters1/5

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

With 0% schema description coverage and 5 parameters, the description adds no meaning beyond the schema. Only 'ref_image' is indirectly explained by 'matching a reference design image's style and colors'. Prompts, aspect, out_pptx, out_dir are unmentioned.

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 'Generate a deck matching a reference design image's style and colors (content not copied)' clearly states the specific verb ('Generate'), resource ('deck'), and what distinguishes it from similar tools (style matching, not content copying).

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

Usage Guidelines3/5

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

The description implies usage context (when you want a deck styled like a reference image) but provides no explicit guidance on when to use this tool versus siblings like branded_deck or generate_slide_deck, nor any exclusion criteria.

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