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 (fill, bold, contrast-checked text), body font and colour (Arabic cells get the Arabic font), alternate-row banding, number columns right-aligned.

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

NameRequiredDescriptionDefault
kitNoA design kit: a name from iwork_list_design_kits (preset or saved, e.g. "executive", "Acme") 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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.6.1
    • changedInput schema / properties / kit / description
      Previous 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."New value: +"A design kit: a name from iwork_list_design_kits (preset or saved, e.g. \"executive\", \"Acme\") or your own {\"fonts\": {...}, \"colors\": {\"title\": \"#RRGGBB\", ...}}. Contrast is checked."
  2. 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."
  3. 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 declare destructiveHint=true and readOnlyHint=false, and the description usefully narrows that blast radius: 'Values never change; every other table is verified untouched' and 'No app needed'. It also explains that dry_run works on a throwaway copy that runs every check. What is missing is anything about failure modes or the response shape for a partial apply, but the safety-relevant behavior is well disclosed.

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 readable, but redundant: the closing parenthetical '(header band, fonts, banding, aligned numbers)' re-lists what the opening sentence already enumerated, and 'Preview with dry_run' repeats the earlier 'dry_run=true previews the change on a copy'. Tightening would remove two restatements with no loss of meaning.

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?

With six parameters at full schema coverage and an output schema present, the description need not explain returns. It covers purpose, scope, sibling routing, preview workflow, and the safety envelope for a destructive mutation. Slightly incomplete on what happens if a partial apply fails or what 'contrast-checked' means when a check fails.

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 and the schema already documents kit, path, sheet, table, banding, and dry_run in detail. The description restates the kit concept ('design kit') and the dry_run preview semantics but adds no format, syntax, or default information beyond what the schema provides.

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?

Names a specific verb and resource with scope: 'Style a whole table from a design kit', then enumerates exactly what that entails (header band, body font/colour, banding, number alignment). It explicitly differentiates from the sibling that does the adjacent job ('For a few cells use numbers_set_cell_style'), so an agent can route 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?

States the selection condition ('Use to make a whole table look designed in one call'), names the alternative for the narrow case (numbers_set_cell_style), and gives the preview prerequisite ('Preview with dry_run'). Both when-to-use and when-to-use-something-else are present.

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