Skip to main content
Glama

Coline

Add a sheet automation

create_sheet_automation

When a row is added or a cell changes (optionally only when conditions match), set, clear, stamp or copy cells, or add a row.

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>",
      "tableId": "<tableId>",
      "name": "<name>",
      "trigger": "<trigger>",
      "actions": "<actions>"
    },
    "name": "create_sheet_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
actionsYes
enabledNo
sheetIdYesSheet id from search, fetch or create_sheet.
tableIdYes
triggerYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
conditionsNo
conditionLogicNo

Output Schema

NameRequiredDescriptionDefault
automationYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.9/5.0
Behavior3/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 useful behavior context by enumerating the trigger kinds and the five action kinds plus the optional condition filtering, but it omits operational details such as the max action/condition counts and whether creating a duplicate automation is allowed.

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 compact sentence with the trigger front-loaded ahead of the action list, and no filler. The parenthetical condition clause is slightly dense but earns its place by covering the conditional-filter behavior.

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 mutation tool with a nested oneOf trigger/action schema and low parameter coverage, the description gives a good conceptual frame but omits required identifier context and the enabled/conditionLogic semantics; the output schema means return values need not be explained. It is adequate but leaves notable gaps an agent must fill from the schema alone.

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?

With only 22% schema description coverage across 9 parameters, the description carries real weight and does partly compensate: 'row is added or a cell changes' maps to the trigger oneOf, 'set, clear, stamp or copy cells, or add a row' maps to the action oneOf variants, and 'only when conditions match' maps to conditions/conditionLogic. However it says nothing about name, enabled, workspace, sheetId or tableId, and doesn't clarify trigger sub-shapes like field_value_changed or the create_row target tableId.

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

Purpose3/5

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

The description describes what the automation does (trigger then action) rather than stating the tool's own operation, so the verb 'create/add' comes only from the name and title. An agent can infer this creates an automation, but it never says so explicitly and does not distinguish it from update_sheet_automation or delete_sheet_automation.

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 guidance, no prerequisites (e.g. needing an existing sheet/table), and no mention of the sibling tools that modify or remove automations. The only hint is the trigger/action phrasing, which implies creation but leaves selection between siblings to inference.

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