Skip to main content
Glama

Visible ranges after hiding worksheet rows

bpj_sheet_visible_ranges
Read-onlyIdempotent

Exclude a list of hidden worksheet row numbers and coalesce adjacent visible rows.

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>",
      "hidden": "<hidden>"
    },
    "name": "bpj_sheet_visible_ranges"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYes
hiddenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety is covered. The description adds the one behavioral detail annotations cannot convey — that adjacent visible rows are merged into coalesced ranges — but says nothing about output shape, ordering, or handling of out-of-range or duplicate row numbers.

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 front-loaded sentence with no filler. It is efficient, though efficiency here reflects under-specification rather than disciplined brevity.

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 should describe the returned structure (a list of A1 row ranges, presumably), and with 0% parameter coverage it should explain the 'hidden' encoding. Neither is present, leaving key call-shaping details to guesswork.

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%, so the description must carry the burden, yet it only loosely gestures at the parameters. The critical ambiguity is the 'hidden' string format (comma-separated numbers? ranges like '5-9'? whitespace?) and the interaction between 'range' and 'hidden' rows outside that range, neither of which is resolved.

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 description names an operation (exclude hidden rows, coalesce adjacent visible rows) on a worksheet range, which is more specific than the title alone, but it never states the deliverable — a list of visible row ranges — and gives no differentiation from siblings such as bpj_sheet_subtract or bpj_sheet_qualify_range.

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 guidance on when to use this versus alternatives, no preconditions (must the range be a full-row span?), and no note on what happens if hidden rows fall outside the range.

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.