Skip to main content
Glama

Coline

Read sheet rows

list_sheet_rows
Read-onlyIdempotent

One page of a sheet table's rows, for the sheet editor in the chat.

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": "list_sheet_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
sheetIdYesSheet id from search, fetch or create_sheet.
tableIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
rowsYes
hasMoreYes
revisionNo
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only that results are paged ("one page"); it says nothing about ordering, default page size, or cursor behavior, which are the remaining traits an agent would want.

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 short sentence with no filler, and the resource scope is front-loaded. Its brevity is close to appropriate, though the sentence carries almost no operational information.

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?

An output schema exists, so return values need not be explained, but a 5-parameter paged-list tool with only 40% schema coverage needs more than one clause. Nothing explains the after/limit interaction or typical usage context, leaving the definition under-specified for its complexity.

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 40%: workspace and sheetId are documented in the schema, but after, limit, and tableId are not. The description never mentions these parameters, so the pagination cursor and page-size controls remain undocumented in both places, which is a meaningful gap for a paged-list tool.

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 phrase "One page of a sheet table's rows" identifies the resource (sheet table rows) and implies retrieval with pagination, but there is no explicit verb and nothing distinguishes this from siblings like read_sheet or list_sheet_history. An agent can guess the purpose but cannot confidently pick it over neighbors from the text alone.

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?

"for the sheet editor in the chat" is a faint contextual hint, not guidance. There is no statement of when to use this versus read_sheet, list_sheet_history, or update_sheet_rows, and no prerequisites or exclusions are given.

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