Skip to main content
Glama

Coline

Comment on a sheet

comment_on_sheet

Adds a comment to a sheet table, row or cell, or a reply to one; mentioned people are notified.

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>",
      "body": "<body>"
    },
    "name": "comment_on_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
rowIdNo
fieldIdNo
sheetIdYesSheet id from search, fetch or create_sheet.
tableIdYes
parentIdNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
mentionedUserIdsNo

Output Schema

NameRequiredDescriptionDefault
commentYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive mutation that is not idempotent. The description adds useful behavior beyond annotations by stating that mentioned people are notified, but it does not cover permissions, duplicate-comment behavior, edit/delete implications, or rate limits.

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 description is a single front-loaded sentence with no filler. Every clause adds relevant scope or behavior, and nothing is wasted.

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?

For an 8-parameter mutation tool with low schema description coverage, the definition is too sparse. The output schema and annotations reduce the burden for return values and safety, but key invocation details such as required tableId semantics, parentId usage for replies, and mentionedUserIds behavior remain under-explained.

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 low at 25%, so the description should compensate for 8 parameters and only 4 required fields. It hints at row/cell targeting, replies, and mentions, but does not map these to rowId, fieldId, parentId, or mentionedUserIds, nor does it clarify why tableId is required for row and cell comments.

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 a specific verb and resource: adding a comment to a sheet table, row, or cell, or a reply. It distinguishes this from other comment tools by naming sheet targets, though it does not explicitly contrast with siblings such as update_sheet_comment or comment_on_change_request.

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?

It implies that the tool is used for sheet comments and replies, but gives no explicit when-to-use guidance, no alternatives, and no prerequisites. An agent must infer when to choose this over list/update/delete sheet comment tools or other comment_* tools.

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