Skip to main content
Glama
Sign In
keynote-mcp

keynote-mcp

by ByAxe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_shape

Add a rectangle shape to a Keynote slide with customizable position, size, and transparency for visual enhancement.

Instructions

Create a rectangle shape with optional position, size, and opacity

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": {
      "slide_number": "<slide_number>"
    },
    "name": "add_shape"
  }
}

Input Schema

NameRequiredDescriptionDefault
slide_numberYesSlide number
xNoX coordinate in pixels (optional)
yNoY coordinate in pixels (optional)
widthNoWidth in pixels (optional, default 200)
heightNoHeight in pixels (optional, default 200)
opacityNoOpacity value 0-100 (optional, default 100)
doc_nameNoDocument name (optional, defaults to front document)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/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 states 'Create a rectangle shape' which implies a write/mutation operation, but doesn't disclose behavioral traits like whether this requires specific permissions, if it modifies existing slides, what happens on failure, or if there are rate limits. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence that front-loads the core purpose ('Create a rectangle shape') and briefly notes key optional parameters. There's zero wasted text, making it appropriately sized and well-structured for quick comprehension.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., success confirmation, shape ID), error conditions, or dependencies like requiring an open presentation. For a 7-parameter tool that modifies presentations, more contextual information is needed.

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 schema already documents all 7 parameters thoroughly. The description mentions 'optional position, size, and opacity,' which loosely maps to x, y, width, height, and opacity parameters, but adds no meaningful semantics beyond what the schema provides (e.g., no clarification on coordinate systems or unit details). Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the action ('Create a rectangle shape') and specifies the resource type ('shape'), which distinguishes it from sibling tools like add_image or add_text_box. However, it doesn't explicitly differentiate from other shape-related tools that might exist (though none are listed in siblings), making it clear but not fully sibling-differentiated.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an open presentation), exclusions, or comparisons to other tools like add_build_in or add_image. This leaves the agent without context for tool selection.

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