Skip to main content
Glama

Coline

Apply sheet edits

apply_sheet_operations
DestructiveIdempotent

Applies the person's edits from the sheet editor in the chat, as one batch.

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>",
      "operations": "<operations>"
    },
    "name": "apply_sheet_operations"
  }
}

Input Schema

NameRequiredDescriptionDefault
sheetIdYesSheet id from search, fetch or create_sheet.
clientIdNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
mutationIdNo
operationsYes

Output Schema

NameRequiredDescriptionDefault
appliedYes
revisionYes
createdIdsYes

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 destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds one genuinely useful trait beyond that - that the operations are applied "as one batch" - but says nothing about atomicity guarantees, partial-failure behavior, or what data is destroyed, which matters for a destructive mutation.

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?

One short sentence with no wasted words, and the batch semantic is front-loaded. Brevity is appropriate here, though it leans toward under-specification rather than crispness.

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

Completeness2/5

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

This is a destructive, multi-parameter mutation whose payload shape (a free-form operations array up to 200 items) is entirely unexplained. Even with an output schema covering returns and annotations covering safety, an agent cannot know what a valid operation object looks like or whether failures are all-or-nothing.

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 coverage is only 40%, and the most important parameter, operations, is an untyped array of free-form objects that the description never explains at all. The clientId and mutationId parameters are undocumented in both schema and description, so the definition does not compensate for the coverage gap.

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?

The description gives a concrete verb ("applies") and resource ("the person's edits from the sheet editor in the chat"), and the phrase "as one batch" hints at how it differs from per-row siblings like update_sheet_rows. It stops short of naming any alternative explicitly, so differentiation is implied rather than stated.

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 condition telling the agent when to pick this over update_sheet_rows, and no prerequisites or follow-up steps mentioned. The agent must infer the routing decision entirely on its own.

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