Skip to main content
Glama

Enumerate selection diagonal cells

bpj_sheet_diagonal_cells
Read-onlyIdempotent

List top-left to bottom-right diagonal cells until reaching the edge of the selection.

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_diagonal_cells"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds one behavioral fact beyond that: enumeration terminates at the selection edge. It omits the output shape (cell addresses? values?), ordering guarantees, and any error behavior for degenerate single-cell ranges.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, which is structurally clean. But the brevity comes at the cost of substance: the one sentence leaves key terms ("selection") undefined, so concision here shades into under-specification.

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?

For a one-parameter, no-output-schema tool the description should at minimum define the range format, the termination semantics on non-square ranges, and what is returned. None of that is present, and "selection" remains ambiguous relative to the "range" input. The rich annotations cover only safety, not semantics.

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 0% for the single required parameter, so the description carries the full burden — and it never mentions "range" at all. The schema title says "A1 rectangular range" with maxLength 160, but the description does not confirm the A1 format, whether the range must be square, or what happens to the diagonal of a non-square range. It adds no meaning beyond the bare schema.

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 verb "List" plus "diagonal cells" gives a concrete operation, and "top-left to bottom-right" pins down which diagonal. However, "selection" is never defined — the tool takes a "range" parameter, so an agent cannot tell whether the selection is the input range, a current editor selection, or something derived. It also does not distinguish itself from geometric siblings such as bpj_sheet_intersection or bpj_sheet_transpose_footprint.

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 and no mention of any alternative tool or precondition. The agent must guess at which point this diagonal enumeration is preferable to the many other sheet-geometry siblings. Only the implicit scoping phrase "until reaching the edge of the selection" hints at a use case.

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.