Skip to main content
Glama

Bounding rectangle of selections

bpj_sheet_bounding_box
Read-onlyIdempotent

Find the smallest rectangle enclosing all supplied selections.

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

Input Schema

NameRequiredDescriptionDefault
rangesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only a restatement of the pure computation and says nothing about the return form (presumably an A1 range) or how multi-sheet selections are handled. With rich annotations, this modest addition earns a baseline 3.

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?

A single front-loaded sentence with no wasted words. It is tight but underspecified rather than padded, so it scores well on economy without earning the top mark.

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 say what the result looks like (e.g. an A1 range or null when nothing is supplied) and whether ranges may span sheets. For a geometry tool with an undocumented parameter and no return description, it leaves real gaps.

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?

There is one required parameter with 0% schema description coverage; only the title 'List of A1 ranges' and a maxLength hint at its format. The description's phrase 'all supplied selections' implies multiple ranges may be passed but does not state the delimiter or accepted A1 syntax, so it only partially compensates.

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?

States a specific verb+resource: 'Find the smallest rectangle enclosing all supplied selections.' An agent knows this computes a bounding box over selection geometry. It does not differentiate from nearby siblings such as bpj_sheet_dimensions or bpj_sheet_qualify_range, which could plausibly overlap.

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?

No guidance on when to use this versus related range-geometry tools, and no mention of constraints such as whether all ranges must lie on one sheet. The sentence only describes the computation, leaving selection among siblings to inference.

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.