Skip to main content
Glama

Coline

Edit or resolve a sheet comment

update_sheet_comment
Idempotent

Edits the person's own comment, or resolves or reopens a thread.

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>",
      "commentId": "<commentId>"
    },
    "name": "update_sheet_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
sheetIdYesSheet id from search, fetch or create_sheet.
resolvedNo
commentIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
commentYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare the tool is non-read-only, idempotent, and non-destructive. The description adds the meaningful ownership restriction ('person's own comment') and thread-state behavior, but it does not explain permission failures, whether other users' comments are rejected, or what exactly changes when resolving.

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?

The definition is a single concise sentence with no redundant wording and the core operations are front-loaded. It is appropriately sized for the information it chooses to convey.

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 five parameters and an output schema, the description covers the main operations but omits important details such as which parameters are required for which mode and how ownership or permission failures behave. It is minimally adequate but not complete.

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 40%, so the description needs to compensate for five parameters. It only vaguely implies a body for edits and a resolved state for resolving or reopening, while leaving commentId, sheetId, workspace, and required/optional relationships largely unexplained beyond the schema.

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 states specific actions—editing the user's own comment and resolving or reopening a thread—on the implied resource of a sheet comment. It is clear, though it does not explicitly distinguish itself from sibling tools such as comment_on_sheet or delete_sheet_comment.

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

Usage Guidelines3/5

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

Usage is implied by the stated operations: editing one's own comment or changing thread resolution. However, there is no explicit guidance on when to choose this over creating, deleting, or otherwise commenting on a sheet.

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