Skip to main content
Glama

Distinct cells across selections

bpj_sheet_distinct_cell_count
Read-onlyIdempotent

Measure the union of rectangles using row bands and merged column intervals without enumerating the cells.

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": {
      "ranges": "<ranges>"
    },
    "name": "bpj_sheet_distinct_cell_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed world), so the bar is lower. The description does add two real behavioral facts: overlapping ranges are unioned (duplicates counted once) and the computation avoids per-cell enumeration for performance — but it says nothing about invalid input handling or the shape of the result.

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 dense sentence with no filler, and the core operation is front-loaded. The trailing clause about row bands and merged column intervals is implementation detail that helps explain the "without enumerating" guarantee, though it is the least useful part for an agent.

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 single-parameter, no-output-schema counting tool, the description leaves two important gaps: the string format used to supply multiple A1 ranges, and the fact that the return value is a scalar count. The algorithm commentary is supplied while the practically necessary input and output semantics are not.

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

Parameters4/5

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

With a single parameter and 0% schema description coverage, the description partially compensates by framing the input as a set of rectangles whose union is measured, which conveys that multiple ranges are expected. It stops short of describing how the A1 ranges are delimited in the single string, but the property title "List of A1 ranges" fills that gap.

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?

"Measure the union of rectangles" gives a verb and an implied resource, but never states that the result is a COUNT of distinct cells, nor that the rectangles come from cell ranges — the reader must lean on the tool name and title to reconstruct that. It also gives no differentiation from nearby siblings such as bpj_sheet_intersection or bpj_sheet_bounding_box, which also take multiple ranges.

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?

The phrase "without enumerating the cells" hints at a fast alternative to enumeration, but no explicit when-to-use, when-not-to-use, or named alternative is given. An agent must guess whether to call this instead of bpj_sheet_enumerate or bpj_sheet_intersection.

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.