Skip to main content
Glama
Sign In

Onplana

by io.github.Onplana
OverviewDiscussionsAdmin

list_workspace_rows

Read-onlyIdempotent

List rows in a workspace table (with cells), in list order. A NUMBER cell is a number, null when empty or not a number; other cells are text. Cursor pagination: cursor takes the nextCursor of the previous page, which is null on the last page. PREFER get_workspace_table for small tables where the full shape is more useful.

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": {
      "tableId": "<tableId>"
    },
    "name": "list_workspace_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 100, max 500.
cursorNo
tableIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds return-value semantics (NUMBER cells are numbers/null, other cells text) and pagination behavior (cursor comes from nextCursor, null on last page). It does not cover error cases, but annotations lower the bar.

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?

Three tight sentences, front-loaded with purpose, then return typing, pagination, and a routing preference. Every sentence adds value and there is no filler, though the density is slightly high.

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

Completeness4/5

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

No output schema exists, so the description carries the return burden. It explains cell typing and pagination and points to get_workspace_table for full shape, making it complete enough for a paginated list tool. Annotations cover safety.

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

Parameters3/5

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

Schema coverage is 33% (only limit is described). The description compensates for cursor with detailed semantics and implies tableId via 'workspace table', but does not explain tableId format or limit (schema covers limit). Compensation is partial given the low coverage.

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?

States a specific verb (List) and resource (rows in a workspace table), including that cells are included and list order is used. It does not explicitly contrast with sibling list_workspace_tables, but the resource and operation are clear enough for an agent to distinguish.

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

Usage Guidelines4/5

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

Explicitly recommends get_workspace_table for small tables where the full shape is more useful, giving a clear conditional alternative. It does not state when-not for other siblings like list_workspace_tables, but that sibling serves a different resource (tables vs rows).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Onplana toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources