Skip to main content
Glama

Tile a selection into blocks

bpj_sheet_tile
Read-onlyIdempotent

Partition a rectangular selection into bounded row-major blocks, including partial edges.

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>",
      "height": "<height>",
      "width": "<width>"
    },
    "name": "bpj_sheet_tile"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYes
widthYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed operation, so the safety profile is covered. The description adds useful behavioral detail beyond that by specifying row-major ordering and inclusion of partial edge blocks, but it does not describe the return value, block count, or validation behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single front-loaded sentence with no filler. Every phrase contributes: the operation, the input shape, the ordering, the block bound, and the edge-case handling.

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?

The tool has three required parameters and no output schema, so the description should explain enough about the result shape, but it does not. It also omits what happens when height/width are larger than the range or how partial edge blocks are represented, leaving the definition under-specified for a computation whose output is not otherwise documented.

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 parameter meaning. It only loosely maps 'rectangular selection' to the range and 'bounded blocks' to height/width, leaving a critical ambiguity: whether height and width define block dimensions or the number of tile rows and columns.

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?

The description gives a specific verb ('Partition') and resource ('a rectangular selection') and states the output form: bounded row-major blocks with partial edges. It is clear what the tool does, though it does not explicitly distinguish itself from nearby range operations such as split_at_cell.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the purpose: an agent can infer it should call this when a rectangular selection needs to be broken into blocks. However, there is no explicit when-to-use guidance, no mention of alternatives, and no prerequisite or exclusion information.

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.