Skip to main content
Glama
Arkanji

iWork Studio MCP Server

by Arkanji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Numbers: set borders

numbers_set_borders
Destructive

Set cell borders on a range in .numbers files: choose sides (outline, inner), width, color, and line style. Preview changes with a dry run before editing.

Instructions

Cell borders on a range: sides = all | outline | inner | top | right | bottom | left; width in points; color "#RRGGBB"; style = solid | dashes | dots | none. dry_run=true previews the change on a copy without touching the file. Use for lines around or inside a range. For fills and fonts use numbers_set_cell_style.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the .numbers file (absolute, or starting with ~).
cellsYesA cell or range in A1 notation, e.g. "B2" or "A1:D1".
colorNoLine colour "#RRGGBB".#000000
sheetNoSheet name. Omit when the file has one sheet (iwork_read lists sheets and tables).
sidesNoall | outline | inner | top | right | bottom | left.all
styleNosolid | dashes | dots | none (none removes the border).solid
tableNoTable name on that sheet. Omit when the sheet has one table.
widthNoLine width in points.
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. Changed9 schema fields changedv2.4.1
    • addedInput schema / properties / cells / description
      Added value: +"A cell or range in A1 notation, e.g. \"B2\" or \"A1:D1\"."
    • addedInput schema / properties / color / description
      Added value: +"Line colour \"#RRGGBB\"."
    • 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 / sides / description
      Added value: +"all | outline | inner | top | right | bottom | left."
    • addedInput schema / properties / style / description
      Added value: +"solid | dashes | dots | none (none removes the border)."
    • addedInput schema / properties / table / description
      Added value: +"Table name on that sheet. Omit when the sheet has one table."
    • addedInput schema / properties / width / description
      Added value: +"Line width in points."
  2. First observedv2.4.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds real value beyond them by explaining that dry_run previews on a throwaway copy and returns what would change without touching the file — a meaningful behavioral contract for a mutating tool.

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?

Terse and front-loaded: option values, then the dry_run safety note, then the routing hint. Dense but every clause carries information; the semicolon list is compact rather than rambling.

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 an output schema present and annotations covering the mutation profile, the description supplies the remaining pieces an agent needs: option vocabularies, dry-run preview semantics, and sibling routing. A brief note on permissions or reversibility would make it fully complete.

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 is already documented, including the sides/style enumerations which the description merely restates. The description adds no syntax, constraint, or default behavior beyond what the schema provides, so 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?

States a precise verb+resource ('cell borders on a range') and immediately scopes the alternatives that distinguish it from siblings (fills/fonts → numbers_set_cell_style). An agent can route correctly 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the when ('use for lines around or inside a range') plus a named alternative for adjacent tasks, and explains when to use dry_run ('before broad or risky edits, show the user'). No explicit when-not condition is stated, so it stops short of the top mark.

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