Skip to main content
Glama
Arkanji

iWork Studio MCP Server

by Arkanji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Numbers: add table

numbers_add_table
Destructive

Add a new table with data to an existing or new sheet in a Numbers file, verifying existing tables stay unchanged. Use dry_run to preview changes on a copy before editing.

Instructions

Add a table with data to an existing sheet (sheet, default the first) or to a new sheet (new_sheet). Every existing table is verified unchanged. dry_run=true previews the change on a copy without touching the file. Use for a new, separate table on a sheet or a new sheet. To grow an existing table use numbers_insert.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the .numbers file (absolute, or starting with ~).
rowsYesThe data, header first: [["Region", "Revenue"], ["Riyadh", 1200]].
sheetNoExisting sheet to add it to; omit for the first sheet.
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.
new_sheetNoName of a new sheet to create for the table instead.
table_nameYesName of the new table (must not exist on that sheet).
header_rowsNoHow many rows at the top are headers (styled and kept on top).
header_columnsNoHow many columns on the left are headers.

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 / 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 / header_columns / description
      Added value: +"How many columns on the left are headers."
    • addedInput schema / properties / header_rows / description
      Added value: +"How many rows at the top are headers (styled and kept on top)."
    • addedInput schema / properties / new_sheet / description
      Added value: +"Name of a new sheet to create for the table instead."
    • addedInput schema / properties / path / description
      Added value: +"Path to the .numbers file (absolute, or starting with ~)."
    • addedInput schema / properties / rows / description
      Added value: +"The data, header first: [[\"Region\", \"Revenue\"], [\"Riyadh\", 1200]]."
    • addedInput schema / properties / sheet / description
      Added value: +"Existing sheet to add it to; omit for the first sheet."
    • addedInput schema / properties / table_name / description
      Added value: +"Name of the new table (must not exist on that sheet)."
  2. First observedv2.4.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag it as destructive and non-idempotent; the description adds genuinely new behavior with 'Every existing table is verified unchanged' and the guarantee that dry_run operates on a copy without touching the file. It stops short of naming what gets destroyed or any permission requirements, but the added context is substantive.

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?

Four short sentences, front-loaded with the core action, then verification semantics, then the routing rule. Every sentence carries distinct information with no repetition.

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?

An output schema exists so return values need no explanation, and the annotations cover the safety profile. The description closes the remaining gaps: placement targets, dry_run behavior, and the sibling boundary. 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.

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description echoes the sheet-vs-new_sheet choice and dry_run semantics but adds no syntax, format or constraint detail beyond what the schema already states.

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 table with data') plus the two placement targets, and explicitly routes the agent to the sibling 'numbers_insert' for the adjacent operation. An agent can distinguish it from numbers_insert without reading either 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 explicit when-to-use ('a new, separate table on a sheet or a new sheet') and when-not ('To grow an existing table use numbers_insert'), and also tells the agent when to reach for dry_run. Nothing 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