Skip to main content
Glama
Arkanji

iWork Studio MCP Server

by Arkanji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Numbers: delete

numbers_delete
Destructive

Deletes rows or columns from a Numbers file at a given position. Refuses tables with formulas or merged cells; undo with iwork_restore_backup. Use dry_run to preview changes.

Instructions

Delete count rows or columns (what = rows | columns) starting at 1-based position at. Remaining cells are verified. Refused in tables with formulas or merged cells. Undo with iwork_restore_backup. dry_run=true previews the change on a copy without touching the file. Use to remove rows or columns. Not for clearing values (use numbers_edit_cell with null). Refused in tables with formulas or merges; undo with iwork_restore_backup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
atYes1-based position of the first one to delete.
pathYesPath to the .numbers file (absolute, or starting with ~).
whatYesrows | columns.
countNoHow many to delete.
sheetNoSheet name. Omit when the file has one sheet (iwork_read lists sheets and tables).
tableNoTable name on that sheet. Omit when the sheet has one table.
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.4.1
    • addedInput schema / properties / at / description
      Added value: +"1-based position of the first one to delete."
    • addedInput schema / properties / count / description
      Added value: +"How many to delete."
    • 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 / path / description
      Added value: +"Path to the .numbers file (absolute, or starting with ~)."
    • addedInput schema / properties / sheet / description
      Added value: +"Sheet name. Omit when the file has one sheet (iwork_read lists sheets and tables)."
    • addedInput schema / properties / table / description
      Added value: +"Table name on that sheet. Omit when the sheet has one table."
    • addedInput schema / properties / what / description
      Added value: +"rows | columns."
  2. First observedv2.4.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, readOnlyHint=false, and idempotentHint=false, and the description adds context the annotations cannot: remaining cells are verified, the operation is refused on tables with formulas or merged cells, undo is available via iwork_restore_backup, and dry_run acts on a throwaway copy. This is rich behavioral disclosure beyond the structured hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and mostly tight, but the tail is wasted: 'Refused in tables with formulas or merged cells. Undo with iwork_restore_backup.' is stated twice (once mid-sentence, once at the end). Duplicated content costs it a point or two.

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 not be explained, and the description covers everything else an agent needs: scope, refusal conditions, reversibility, and dry-run workflow. Nothing material is missing for a destructive single-operation 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 description coverage is 100%, so all seven parameters are already documented; the description repeats at/what/count/dry_run rather than adding new semantics like edge-case behavior for out-of-range positions or count defaults. Baseline 3 is correct when the schema does the heavy lifting.

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 (delete) plus resource (rows/columns) and the exact scoping parameters (count, what, 1-based at). It clearly separates itself from the sibling numbers_edit_cell by naming it as the tool for clearing values instead.

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?

Explicitly gives when-not-to-use ('Not for clearing values (use numbers_edit_cell with null)') and when-to-verify ('dry_run=true previews the change... Use before broad or risky edits'). The alternative for clearing is named with the exact tool and parameter (null).

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