Skip to main content
Glama
Sign In
ChatPPT

ChatPPT

by ParkerDiamond
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

slide_render

Read-only

Render a presentation slide as a PNG image preview to visually verify layout and content before finalizing a deck.

Instructions

Render a slide to a PNG image preview for visual feedback.

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": {
      "deckId": "<deckId>",
      "slideId": "<slideId>"
    },
    "name": "slide_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthNoLegacy output width in pixels; resolution takes precedence
deckIdYesStable ID of the presentation deck
slideIdYesStable ID of the slide to render
filePathNoOptional PNG output path inside the managed workspace; .png is added or substituted
resolutionNoOptional output width in pixels; defaults to 1280

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With readOnlyHint=true already declaring this a safe read, the description adds the useful behavioral fact that the product is a rendered image rather than slide data. It does not disclose whether the PNG is returned inline or written to the workspace, whether rendering is expensive or cached, or any size/latency characteristics.

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?

A single front-loaded sentence with zero redundant wording; the verb and result come first and every phrase carries information.

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?

There is no output schema, so the description must carry the return-value burden; it does say the result is a PNG preview, but leaves ambiguous whether the image is returned in the response or only written to filePath. For a 5-parameter tool with a file-writing option, that distinction matters to correct invocation.

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 coverage is 100%, so deckId, slideId, width, resolution, and filePath are all documented, including the legacy-vs-resolution precedence rule. The description adds no parameter-level meaning beyond the schema, which is the expected baseline here.

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 names a specific verb and resource ('Render a slide') plus the output artifact ('PNG image preview'), so it is clearly distinct from data-reading siblings like slide_read. It does not explicitly name an alternative, which keeps it just below a 5.

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?

'for visual feedback' implies the use case (you want to see the slide rather than read its structure), but there is no explicit when-to-use vs when-not guidance and no pointer to slide_read for structured content. Usage is inferable rather than stated.

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