Skip to main content
Glama
Sign In
Keynote MCP Server

Keynote MCP Server

by superdwayne
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_table_data

Replaces table content on a Keynote slide with data from a 2D array of strings. Each inner array represents a row of cell values.

Instructions

Bulk-sets table data from a 2D array of strings. Each inner array is a row.

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": {
      "slideIndex": "<slideIndex>",
      "tableIndex": "<tableIndex>",
      "data": "<data>"
    },
    "name": "set_table_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes2D array of strings — each inner array is a row of cell values
slideIndexYes1-based slide index
tableIndexYes1-based table index

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 should disclose mutation behavior. It does not state whether the tool replaces all table data, merges, or requires the table to exist. No mention of side effects, permissions, or limits.

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?

Two concise sentences, front-loaded with the core purpose. No redundant information; each sentence contributes meaning.

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 no output schema and no annotations, the description is insufficient. It does not explain the effect on existing data, prerequisites, or return value, leaving significant gaps for a mutation tool.

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%, and the description does not add meaning beyond what the schema's descriptions already provide. It repeats the concept of a 2D array but adds no new semantic detail.

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 clearly states the tool bulk-sets table data using a 2D array of strings, with each inner array as a row. This effectively distinguishes it from siblings like set_table_cell and get_table_data.

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?

No explicit guidance on when to use this tool vs alternatives (e.g., set_table_cell). The word 'Bulk-sets' implies it's for updating multiple cells at once, but no direct comparison or exclusions are provided.

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