Skip to main content
Glama

Split a selection at a cell

bpj_sheet_split_at_cell
Read-onlyIdempotent

Cut a selection into up to four rectangles with the selected cell starting the bottom-right block.

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>",
      "address": "<address>"
    },
    "name": "bpj_sheet_split_at_cell"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYes
addressYes

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?

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the piece that matters most: the result is at most four rectangles, i.e. it is a computed partition rather than an in-place edit. The verb 'cut' is slightly misleading against readOnlyHint, though it reads as partitioning rather than deletion, so this is ambiguity rather than contradiction.

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 short sentence with no filler, and the core action is front-loaded. The trailing clause is the weakest part, since 'starting the bottom-right block' takes rereading to parse correctly.

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?

For a two-parameter geometric tool with no output schema, the definition should state what the return value looks like (a list of up to four ranges) and describe the edge conditions that determine whether you get two, three, or four pieces. Neither is covered, leaving the agent to guess at return shape and boundary behavior.

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 has to carry the load, and it does partially: 'selection' maps to range, and 'the selected cell' maps to address with the useful detail that it anchors the bottom-right block. It does not explain expected address or range syntax (A1 notation, the 160-character caps) or what happens when the split cell lies on an edge of the range.

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 a specific operation ('cut a selection into up to four rectangles') on a specific resource, but the phrasing 'with the selected cell starting the bottom-right block' is awkward and leaves the exact geometry only loosely inferable. It also gives no differentiation from related siblings such as bpj_sheet_tile, bpj_sheet_subtract, or bpj_sheet_intersection, which appear to operate on the same range primitives.

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 statement of when to use this tool versus the neighboring range tools; the agent must infer from the name alone. No prerequisites, no exclusions, and no mention of what a caller gets that bpj_sheet_subtract or bpj_sheet_tile would not give them.

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.