Skip to main content
Glama
Arkanji

iWork Studio MCP Server

by Arkanji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Numbers: import csv

numbers_import_csv
Destructive

Convert CSV or TSV files into new Apple Numbers spreadsheets, auto-detecting delimiters and optionally converting plain numbers to numeric cells. Refuses to overwrite existing files.

Instructions

Turn a CSV/TSV into a new .numbers file (UTF-8, delimiter auto-detected). Plain numbers become numbers (numbers=false keeps everything as text); dates, "$1,234" and Arabic-Indic digits stay text exactly as written. Refuses to overwrite. Use when the data is in a CSV/TSV file. When you already have the rows use numbers_create.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesWhere to create the new .numbers file; it must not exist yet.
sheetNoName for the new sheet.Sheet 1
tableNoName for the new table.Table 1
numbersNotrue = plain numbers become numbers; false = keep every cell as text.
csv_pathYesThe CSV or TSV file to read (UTF-8).
delimiterNoColumn separator, e.g. "," or "\t"; omit to detect it.
header_rowsNoHow many rows at the top are headers (styled and kept on top).

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 / csv_path / description
      Added value: +"The CSV or TSV file to read (UTF-8)."
    • addedInput schema / properties / delimiter / description
      Added value: +"Column separator, e.g. \",\" or \"\\t\"; omit to detect it."
    • addedInput schema / properties / header_rows / description
      Added value: +"How many rows at the top are headers (styled and kept on top)."
    • addedInput schema / properties / numbers / description
      Added value: +"true = plain numbers become numbers; false = keep every cell as text."
    • addedInput schema / properties / path / description
      Added value: +"Where to create the new .numbers file; it must not exist yet."
    • addedInput schema / properties / sheet / description
      Added value: +"Name for the new sheet."
    • addedInput schema / properties / table / description
      Added value: +"Name for the new table."
  2. First observedv2.4.0

TDQS

A4.6/5.0
Behavior4/5

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

The description goes well beyond the annotations by spelling out value-conversion semantics (plain numbers become numbers, dates / "$1,234" / Arabic-Indic digits stay text) and the no-overwrite guarantee. This is unusually rich for a write tool and useful for predicting results, though it doesn't cover failure modes such as malformed CSV handling.

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

Conciseness5/5

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

Four compact sentences, each carrying distinct information, with the core action and its safety constraint front-loaded before the routing advice. No filler or restatement of the tool name.

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, annotations supplied, and 100% parameter coverage, the description only needs to add conversion and overwrite context, which it does. The remaining gap is minor: no mention of what happens on an invalid or non-UTF-8 source file.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it clarifies the numbers=true/false contract and that the target path must not already exist ("Refuses to overwrite"). It does not explain header_rows or delimiter behavior beyond what the schema already says.

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 gives a specific verb and resource ("Turn a CSV/TSV into a new .numbers file") and immediately scopes it with encoding and detection behavior. It also distinguishes itself from the sibling numbers_create by routing row-based input there, so an agent can pick between the two without opening a 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 the trigger condition explicitly ("Use when the data is in a CSV/TSV file") and names the alternative with its own condition ("When you already have the rows use numbers_create"). The overwrite exclusion is also stated as a rule rather than left to inference.

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