Skip to main content
Glama

Enumerate cells in reading order

bpj_sheet_enumerate
Read-onlyIdempotent

Enumerate up to 500 cells in row-major reading order.

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": {
      "range": "<range>"
    },
    "name": "bpj_sheet_enumerate"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description contributes the 500-cell cap and the row-major ordering, which are useful behavioral facts not in the annotations. However, it does not say what happens when a range exceeds 500 cells (truncation, error, or pagination), which is the key behavioral uncertainty here.

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 well-formed sentence with the limit and ordering front-loaded and no wasted wording. It is efficient, though its brevity is partly the source of the documentation gaps rather than a virtue of precision.

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 simple single-parameter read tool with rich annotations and no output schema, the description covers purpose, cap, and ordering. It is still missing the overflow/truncation behavior that an agent needs in order to call it correctly on large ranges, and gives no hint of the returned cell representation.

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?

There is one parameter with 0% schema description coverage; the schema only supplies a title ('A1 rectangular range') and a maxLength. The description adds no meaning to the range argument — no expected syntax such as sheet-qualified references, no handling of multi-area ranges, and no note on why the 160-character limit exists.

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 uses a specific verb and resource ('Enumerate ... cells') and adds scope (up to 500) plus ordering (row-major). It does not differentiate itself from similar siblings such as bpj_sheet_nth_cell or bpj_sheet_dimensions, so an agent must still infer which cell-oriented tool to pick.

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?

There is no statement of when this tool should be used instead of alternatives, and no exclusions or prerequisites. The reader is left to infer that it suits bulk cell listing rather than single-cell or dimension lookups.

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.