Skip to main content
Glama

Coline

Add sheet columns

add_sheet_columns

Adds columns to a sheet table: a status select, a formula, a date, any typed field.

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": {
      "workspace": "<workspace>",
      "sheetId": "<sheetId>",
      "columns": "<columns>"
    },
    "name": "add_sheet_columns"
  }
}

Input Schema

NameRequiredDescriptionDefault
columnsYes
sheetIdYesSheet id from search, fetch or create_sheet.
tableIdNoA table in the sheet; default: the one it opens on.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
urlYes
sheetIdYes
summaryYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing behavioral beyond that: it does not state that columns are appended, that repeating the call creates duplicates (non-idempotent), the 30-column batch limit, or what happens on name collisions.

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?

A single short sentence, front-loaded with the action and resource, with no filler or redundancy. It is efficient, though its brevity leaves it leaning on the schema for nearly all detail.

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 mutating, non-idempotent batch tool with an output schema and 75% schema coverage, the definition is workable but thin: it omits batching limits, append semantics, and duplicate-name behavior that an agent needs before composing a call. The output schema relieves it of explaining return values.

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 coverage is 75%, so workspace, sheetId, tableId, formula, and options are already documented in the schema. The description's mention of 'a status select, a formula, a date, any typed field' loosely hints at the type/formula/options interaction but gives no specifics on how the type enum drives which nested fields are required.

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 concrete verb ('Adds') and resource ('columns to a sheet table') and enumerates example column kinds (status select, formula, date, typed field), so an agent can distinguish it from row/data-mutation siblings. It stops short of naming which sibling applies to a different shape of work.

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 explicit when-to-use or when-not-to-use guidance, no mention of prerequisites (workspace slug, sheetId obtained from search/fetch/create_sheet), and no routing to alternatives such as apply_sheet_operations, which a sibling context suggests may overlap structurally. Usage is only inferable from the tool name and verb.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources