Skip to main content
Glama
Arkanji

iWork Studio MCP Server

by Arkanji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Keynote: add chart

keynote_add_chart
Destructive

Add a chart to an existing Keynote slide from row/column data, with options for chart type and grouping. Preview changes on a copy before applying.

Instructions

Add a chart to a slide from data. rows = series names, columns = category names, data = one list of numbers per row (rows × columns). type: bar | stacked_bar | horizontal_bar | stacked_horizontal_bar | line | area | stacked_area | pie | scatter (or *_3d). group_by: row | column. Text and other charts are verified untouched. dry_run=true previews the change on a copy without touching the file. Use for a chart on an existing slide. In a new deck, put the chart in keynote_build_deck's outline instead; for exact numbers use keynote_add_table.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesOne list of numbers per row name, each as long as columns.
pathYesPath to the .key deck (absolute, or starting with ~).
rowsYesRow names, e.g. ["2025", "2026"] (series when group_by="row").
typeNobar | stacked_bar | horizontal_bar | stacked_horizontal_bar | line | area | stacked_area | pie | scatter (or a *_3d variant).bar
slideYesSlide number, 1-based (keynote_list_slides lists them).
columnsYesColumn names, e.g. ["Q1", "Q2", "Q3"].
dry_runNotrue = make the change on a throwaway copy, run every check, and return what would change; the file itself is not touched. Use it before broad or risky edits and show the user.
group_byNorow (each row is a series) | column.row

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.4.1
    • addedInput schema / properties / columns / description
      Added value: +"Column names, e.g. [\"Q1\", \"Q2\", \"Q3\"]."
    • addedInput schema / properties / data / description
      Added value: +"One list of numbers per row name, each as long as columns."
    • addedInput schema / properties / dry_run / description
      Added value: +"true = make the change on a throwaway copy, run every check, and return what would change; the file itself is not touched. Use it before broad or risky edits and show the user."
    • addedInput schema / properties / group_by / description
      Added value: +"row (each row is a series) | column."
    • addedInput schema / properties / path / description
      Added value: +"Path to the .key deck (absolute, or starting with ~)."
    • addedInput schema / properties / rows / description
      Added value: +"Row names, e.g. [\"2025\", \"2026\"] (series when group_by=\"row\")."
    • addedInput schema / properties / slide / description
      Added value: +"Slide number, 1-based (keynote_list_slides lists them)."
    • addedInput schema / properties / type / description
      Added value: +"bar | stacked_bar | horizontal_bar | stacked_horizontal_bar | line | area | stacked_area | pie | scatter (or a *_3d variant)."
  2. First observedv2.4.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and non-idempotency; the description adds meaningful context beyond them by promising that text and other charts are 'verified untouched' and by explaining that dry_run=true previews on a throwaway copy and returns what would change. It still doesn't cover permissions or what happens on a malformed data shape, so it stops short of a 5.

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?

Front-loaded with the core action and data model, then usage routing and safety notes; every sentence carries information. It is somewhat dense and repeats the full type enum already present in the schema, which is the only real waste.

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

Completeness5/5

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

For an 8-parameter mutation tool with a full output schema, the description covers the data shape, chart-type options, grouping semantics, the dry_run safety valve, verification of untouched content, and sibling alternatives. An agent has everything needed to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds semantics: it clarifies that rows are series when group_by='row' and that data holds one list of numbers per row name, which is the relationship the schema only states piecewise. It also restates the type enum, which is mild redundancy rather than new information.

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?

States a specific verb and resource ('Add a chart to a slide from data') and immediately defines the data model (rows = series, columns = categories, data = rows × columns), which is the crux of the operation. It explicitly distinguishes itself from keynote_build_deck and keynote_add_table, so an agent can route without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use condition ('Use for a chart on an existing slide') plus two named alternatives with the conditions that select them: keynote_build_deck for new decks and keynote_add_table for exact numbers. Nothing about selection is left to inference.

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