Skip to main content
Glama
Sign In
Keynote MCP Server

Keynote MCP Server

by superdwayne
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

close_presentation

Close the active Keynote presentation, choosing whether to save changes before closing.

Instructions

Closes the frontmost Keynote presentation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "close_presentation"
  }
}

Input Schema

NameRequiredDescriptionDefault
savingNoWhether to save before closing (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

Without annotations, the description carries full burden but only states the core action. It does not disclose potential side effects (e.g., discarding changes if saving=false), error conditions (e.g., no presentation open), or confirmation behavior.

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 description is one sentence long, efficient, and front-loaded with the action. It is appropriately sized for a simple tool, but lacks any structural elements like bullet points.

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?

Given the tool's simplicity and single optional parameter, the description is adequate but incomplete. It does not mention what happens if no presentation is open or the implications of the saving parameter on user experience.

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?

The input schema fully describes the single parameter with 100% coverage. The description adds no additional meaning beyond 'closes', so the baseline of 3 applies.

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 uses a specific verb ('Closes') and resource ('frontmost Keynote presentation'), clearly distinguishing it from sibling tools like 'open_presentation' or 'save_presentation'.

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 does not specify when or why to use this tool versus alternatives, nor does it mention prerequisites or typical workflows. It lacks explicit guidance on usage context.

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