Skip to main content
Glama

Worksheet selection dimensions

bpj_sheet_dimensions
Read-onlyIdempotent

Normalize the selected rectangle and return its row, column and cell counts.

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

Input Schema

NameRequiredDescriptionDefault
rangeYes

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 declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuine value by disclosing the three return values, but it does not explain what "normalize" actually does to edge cases (whole-column ranges, reversed anchors, whitespace, sheet prefixes).

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 sentence with no filler, and the action is front-loaded ahead of the return values. It is efficient, though the brevity edges into under-specification rather than crispness.

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?

The tool is simple (one required param) and annotations cover the safety profile, so the description needn't be long. However, with no output schema and no explanation of normalization semantics or error behavior for malformed ranges, it stops short of complete.

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%, so the description must carry the parameter's meaning; "the selected rectangle" implies the input is a rectangular reference but adds no format or validation detail beyond the schema's title "A1 rectangular range". This is only marginally compensatory for the coverage 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?

The description names an action ("normalize") and the outputs ("row, column and cell counts"), so the general purpose is inferable, but "the selected rectangle" is vague against a schema whose only input is a string range. It offers no differentiation from nearby siblings such as bpj_sheet_bounding_box, bpj_sheet_qualify_range, or bpj_sheet_distinct_cell_count.

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 stated prerequisite, and no named alternative tool. An agent must guess whether this or bpj_sheet_bounding_box / bpj_sheet_qualify_range is the right call for a given range task.

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.