Skip to main content
Glama

Coline

List sheet comments

list_sheet_comments
Read-onlyIdempotent

Comments on a sheet, or on one row; resolved ones only when asked.

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

Input Schema

NameRequiredDescriptionDefault
rowIdNo
sheetIdYesSheet id from search, fetch or create_sheet.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
includeResolvedNo

Output Schema

NameRequiredDescriptionDefault
commentsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no explanation. The description does add one real behavioral fact not in structured data: resolved comments are excluded by default and only returned when requested. It says nothing about ordering, pagination, or how sheet-wide listing treats row comments, which is the usual gap at this tier.

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 clause-built fragment with zero filler, and the sheet-vs-row scope is front-loaded. It borders on under-specified rather than verbose, but every clause carries distinct information.

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?

An output schema exists, so return shape needs no prose, and the tool is simple. Still missing for correct invocation: result ordering, whether results are paginated or truncated, and whether a sheet-wide listing includes row-level comments. Adequate but not complete for a four-parameter listing tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% – rowId and includeResolved have no schema descriptions – and the description covers both: 'or on one row' explains rowId as a scope narrower, and 'resolved ones only when asked' explains includeResolved as an opt-in defaulting to false. That is meaningful compensation for the two undocumented parameters.

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?

"Comments on a sheet, or on one row" names the resource and the two scopes (sheet-wide vs. row-scoped), which is enough to tell it apart from the mutation siblings like comment_on_sheet and delete_sheet_comment. The verb 'list' is only implicit from the name, but the read intent is unmistakable.

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 rather than stated: you call it to read comments, pass a row to narrow scope, and ask for resolved ones explicitly. No alternative is named and no conditions for choosing row-level vs. sheet-level are given, so the agent has to infer the selection logic.

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