Skip to main content
Glama

Extract the selection perimeter

bpj_sheet_border
Read-onlyIdempotent

Return disjoint range segments around the rectangle perimeter and count boundary 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": {
      "range": "<range>"
    },
    "name": "bpj_sheet_border"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds that the result contains two distinct artifacts (segments and a count), but says nothing about ordering, inclusivity of corners, or how degenerate ranges (single row/column) are treated.

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?

It is a single, front-loaded sentence with no filler, and the primary output (segments) is named before the secondary one (count). The terseness comes at the cost of clarity, but no words are wasted.

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?

There is no output schema, so the description carries the burden of explaining return values, yet it never clarifies the shape or order of the "disjoint range segments" or how the count relates to them. For a computational read tool whose entire value is its output shape, this is a meaningful gap despite the simple one-parameter input.

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 only one parameter and schema coverage is 0%, though its schema title "A1 rectangular range" with maxLength=160 already conveys the accepted format. The description's phrase "rectangle perimeter" confirms the range is interpreted by its outer boundary, adding a little meaning, but it does not explain edge-case handling such as single-cell or non-contiguous input.

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 gives a specific verb ("Return") and a concrete output (disjoint range segments plus a boundary-cell count), which hints at the operation on an A1 range. However, "around the rectangle perimeter" is ambiguous about whether segments are rows, columns, or cells, and it does not contrast itself with nearby siblings such as bpj_sheet_bounding_box or bpj_sheet_visible_ranges, so an agent cannot confidently discriminate it.

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 description provides no when-to-use context, no prerequisites, and no alternatives. There is no statement such as "use this instead of bpj_sheet_bounding_box when you need only the outer ring," so the agent must infer usage from the name and sibling list alone.

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.