Skip to main content
Glama

Find cell at a reading-order index

bpj_sheet_nth_cell
Read-onlyIdempotent

Locate the cell at a one-based row-major position inside a rectangle.

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

Input Schema

NameRequiredDescriptionDefault
indexYes
rangeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds nothing beyond that: it does not say what happens when the index exceeds the range size, whether an error or empty result is returned, or what form the located cell takes. For a lookup tool whose main failure mode is an out-of-bounds index, that gap matters.

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?

One short sentence with no filler, and the key qualifier (one-based row-major position) is front-loaded before the container (rectangle). It is efficient, though the brevity leaves the gaps noted elsewhere rather than being wasteful.

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?

With no output schema, the description must at minimum convey what the call returns (a cell reference, an address, a value?) and how it behaves at boundary indices. Neither is covered, and with 0% schema description coverage on both parameters, the definition is too thin for reliable invocation.

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 description coverage is 0% and the schema only carries titles ("One-based index", "A1 rectangular range"). The description does add real meaning by specifying row-major traversal order and that the index is one-based, which the schema does not state. It says nothing further about the A1 range format or its 160-character limit.

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 gives a concrete verb ("Locate") and resource ("the cell") plus the scoping condition (a one-based row-major position inside a rectangle). It also resolves the ambiguity of the title's "reading-order" by stating row-major explicitly. It stops short of distinguishing this from siblings like split_at_cell or distinct_cell_count, so it is clear but not sibling-differentiated.

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 when-to-use guidance, no prerequisites, and no mention of alternatives or exclusions. An agent has to infer from the name alone whether to use this versus split_at_cell or parse_cell. Only the one-based row-major phrasing implies the applicable context.

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.