Skip to main content
Glama

Build a rectangle from an anchor

bpj_sheet_from_anchor
Read-onlyIdempotent

Build a bounded rectangular selection from its top-left cell and requested dimensions.

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": {
      "address": "<address>",
      "height": "<height>",
      "width": "<width>"
    },
    "name": "bpj_sheet_from_anchor"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthYes
heightYes
addressYes

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile of this pure computation is fully covered structurally. The description adds only the fact that the result is a 'bounded' selection, and says nothing about behavior at sheet limits (width/height maxima) or errors for invalid addresses. With annotations carrying the burden, this is adequate but thin.

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 tight sentence with the key concept (top-left anchor, dimensions) front-loaded and no filler. It is efficiently sized, though brevity comes at the cost of detail handled poorly in other dimensions.

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 simple deterministic three-parameter computation, the essential semantics are present and annotations cover side effects. However, with no output schema the description should say what the returned 'selection' actually looks like (range string, object, etc.), and it says nothing about out-of-bounds behavior — leaving a real gap.

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%, but the schema itself carries titles and min/max bounds for all three parameters. The description's real contribution is clarifying that 'address' is the top-left anchor and that height/width are the requested dimensions of the rectangle — meaning not present in the schema. It does not explain whether limits are validated or how out-of-bounds rectangles behave.

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 and resource: build a bounded rectangular selection from a top-left cell plus dimensions. An agent can tell this apart from generic range siblings like bpj_sheet_bounding_box or bpj_sheet_offset, though the description never names those alternatives explicitly.

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 or when-not-to-use guidance, and no mention of related tools such as bpj_sheet_bounding_box, bpj_sheet_tile, or bpj_sheet_offset that could also produce a rectangle. The intended usage is only implied by the wording.

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.