Skip to main content
Glama
Arkanji

iWork Studio MCP Server

by Arkanji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Numbers: set cell style

numbers_set_cell_style
Destructive

Style specific cells in Apple Numbers by setting font, color, fill, wrap, or alignment on a range. Change only chosen attributes; preview with dry_run before applying.

Instructions

Style a range ("A1:D1"): font_name, font_size, bold, italic, underline, strikethrough, font_color / fill_color as "#RRGGBB", align (left|center|right|justify|auto), valign (top|middle|bottom), wrap. Only the attributes you pass change; every other cell is verified untouched. dry_run=true previews the change on a copy without touching the file. Use for fonts, colours, fill or alignment on a few cells. For a whole table that should look designed use numbers_apply_design; for how numbers display use numbers_set_number_format.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boldNotrue/false; omit to leave as is.
pathYesPath to the .numbers file (absolute, or starting with ~).
wrapNotrue = wrap text in the cell.
alignNoHorizontal: left | center | right | justify | auto.
cellsYesA cell or range in A1 notation, e.g. "B2" or "A1:D1".
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.
italicNotrue/false; omit to leave as is.
valignNoVertical: top | middle | bottom.
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.
font_nameNoFont family, e.g. "Helvetica Neue" or "Geeza Pro".
font_sizeNoFont size in points.
underlineNotrue/false; omit to leave as is.
fill_colorNoCell fill "#RRGGBB".
font_colorNoText colour "#RRGGBB".
strikethroughNotrue/false; omit to leave as is.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changedv2.4.1
    • addedInput schema / properties / align / description
      Added value: +"Horizontal: left | center | right | justify | auto."
    • addedInput schema / properties / bold / description
      Added value: +"true/false; omit to leave as is."
    • addedInput schema / properties / cells / description
      Added value: +"A cell or range in A1 notation, e.g. \"B2\" or \"A1:D1\"."
    • 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 / fill_color / description
      Added value: +"Cell fill \"#RRGGBB\"."
    • addedInput schema / properties / font_color / description
      Added value: +"Text colour \"#RRGGBB\"."
    • addedInput schema / properties / font_name / description
      Added value: +"Font family, e.g. \"Helvetica Neue\" or \"Geeza Pro\"."
    • addedInput schema / properties / font_size / description
      Added value: +"Font size in points."
    • addedInput schema / properties / italic / description
      Added value: +"true/false; omit to leave as is."
    • 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 / strikethrough / description
      Added value: +"true/false; omit to leave as is."
    • addedInput schema / properties / table / description
      Added value: +"Table name on that sheet. Omit when the sheet has one table."
    • addedInput schema / properties / underline / description
      Added value: +"true/false; omit to leave as is."
    • addedInput schema / properties / valign / description
      Added value: +"Vertical: top | middle | bottom."
    • addedInput schema / properties / wrap / description
      Added value: +"true = wrap text in the cell."
  2. First observedv2.4.0

TDQS

A4.4/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing partial-update semantics ("Only the attributes you pass change; every other cell is verified untouched") and the copy-based preview behavior of dry_run. It does not explain reversibility or that the write to the target file is destructive, but the annotation already flags destructiveHint=true, so the remaining gap is minor.

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-loads the range example and the mutation semantics, then the routing guidance, so the most decision-relevant content comes first. The mid-sentence attribute list is dense and partially redundant with the schema, but each clause carries real information.

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 a 16-parameter mutation tool it covers the essentials an agent needs: scope, partial-application behavior, a safe preview mode, and routing to the two nearest siblings. Return values are handled by the output schema and safety by annotations, so nothing critical is missing.

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 one of the 16 parameters (including units like points and #RRGGBB colours) is already documented in the schema. The description's inline enumeration of attributes and allowed values largely repeats that structured data rather than adding new semantics.

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 (style a range in a Numbers file) plus the exact attribute surface, and explicitly distinguishes itself from numbers_apply_design and numbers_set_number_format. An agent can select it without opening the 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 scope rule ("a few cells") and names two alternatives with the condition that selects each: numbers_apply_design for a whole designed table, numbers_set_number_format for display formatting. It also advises dry_run pre-flight before risky edits.

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