Skip to main content
Glama
Arkanji

iWork Studio MCP Server

by Arkanji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Numbers: apply design

numbers_apply_design
Destructive

Style a whole table from a design kit—header band, fonts, row banding, right-aligned numbers—without changing values or other tables. Use dry_run to preview.

Instructions

Style a whole table from a design kit: header band (fill, bold, contrast-checked text), body font and colour (Arabic cells get the Arabic font), alternate-row banding, number columns right-aligned. Values never change; every other table is verified untouched. No app needed. dry_run=true previews the change on a copy without touching the file. Use to make a whole table look designed in one call (header band, fonts, banding, aligned numbers). For a few cells use numbers_set_cell_style. Preview with dry_run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kitNoA design kit: a name from iwork_list_design_kits (preset or saved, e.g. "executive", "Resal") or your own {"fonts": {...}, "colors": {"title": "#RRGGBB", ...}}. Contrast is checked.executive
pathYesPath to the .numbers file (absolute, or starting with ~).
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.
bandingNotrue = tint alternate body rows.
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. Changed6 schema fields changedv2.4.1
    • addedInput schema / properties / banding / description
      Added value: +"true = tint alternate body rows."
    • 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 / kit / description
      Added value: +"A design kit: a name from iwork_list_design_kits (preset or saved, e.g. \"executive\", \"Resal\") or your own {\"fonts\": {...}, \"colors\": {\"title\": \"#RRGGBB\", ...}}. Contrast is checked."
    • 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."
  2. First observedv2.4.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds substantive context the annotations cannot: values are never modified, sibling tables are verified untouched, no host app is required, and dry_run runs all checks on a throwaway copy. It does not explain reversibility or what happens to pre-existing formatting that conflicts with the kit, which keeps it 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.

Conciseness3/5

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

The core content is front-loaded, but the final two sentences restate earlier material: the parenthetical '(header band, fonts, banding, aligned numbers)' repeats the opening list, and 'Preview with dry_run' repeats the dry_run sentence verbatim in substance. Roughly a third of the text is redundant.

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

Completeness4/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 the operation, content preservation, collateral-table safety, the sibling alternative, and the dry_run preview. It stops short of describing what happens when the kit conflicts with existing formatting or whether the operation is repeatable.

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 every parameter (kit, path, sheet, table, banding, dry_run) is already documented in the schema, including the kit's shape and the sheet/table omission rule. The description only restates kit, banding and dry_run at a high level, adding no syntax or format detail beyond the schema; baseline 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 names a specific verb (style) and resource (a whole table) and enumerates the exact transformations applied: header band, body font/colour, banding, right-aligned numbers. It explicitly contrasts scope with numbers_set_cell_style, so an agent can distinguish whole-table styling from cell-level styling without opening 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?

It states when to use it ('to make a whole table look designed in one call') and names the alternative for the opposite case ('For a few cells use numbers_set_cell_style'), plus a preview pathway ('Preview with dry_run'). Both the selection condition and the exclusion are explicit.

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