Skip to main content
Glama
Sign In
apple-productivity-mcp

apple-productivity-mcp

by gambadio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

apple_numbers_create_table

Add a named table without header or footer rows to a Numbers sheet, rejecting duplicate table names.

Instructions

Add a named table without header or footer rows to a Numbers sheet. Rejects duplicate table names.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "documentName": "<documentName>",
      "sheetName": "<sheetName>",
      "tableName": "<tableName>",
      "rows": "<rows>",
      "columns": "<columns>"
    },
    "name": "apple_numbers_create_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnsYes
sheetNameYes
tableNameYes
documentNameYesExact name returned by list_documents; ambiguous duplicate names are rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare the write/non-destructive/non-idempotent profile, and the description adds two real behavioral facts: the table is created without header or footer rows, and duplicate table names are rejected. The rejection rule is especially useful because it explains the non-idempotent hint in practice.

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?

Two tight sentences with the core action first and the error behavior second; no filler or redundancy.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-required-parameter mutation with no output schema and thin parameter documentation, the description leaves the agent guessing about prerequisites (open document? existing sheet?) and about what is returned on success. It covers the write semantics and the duplicate-name failure, but not enough of the call context.

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

Parameters2/5

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

Schema description coverage is only 20% (only documentName is documented), so the description should compensate but does not: it never mentions rows, columns, sheetName, or tableName, nor the 1-1000 row and 1-100 column bounds. Only the vague phrase 'named table' hints at tableName.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (add) and resource (named table) scoped to a Numbers sheet, and clarifies the resulting structure has no header or footer rows. It is distinguishable from apple_numbers_create (document) and apple_numbers_list_tables, though it does not explicitly name those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite (e.g. whether the document must be open first via apple_numbers_open), and no alternative named. The purpose implies the usage but nothing is stated.

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