Skip to main content
Glama

Translate a selection

bpj_sheet_offset
Read-onlyIdempotent

Shift a rectangle by signed row and column offsets while preserving its shape.

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>",
      "rows": "<rows>",
      "cols": "<cols>"
    },
    "name": "bpj_sheet_offset"
  }
}

Input Schema

NameRequiredDescriptionDefault
colsYes
rowsYes
rangeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by saying offsets are 'signed' and that shape is preserved, but it omits what happens when an offset pushes the rectangle outside sheet bounds.

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?

A single, front-loaded sentence with no wasted words. It delivers the core operation immediately and is appropriately sized for a simple geometric transformation.

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?

The tool is simple and read-only, and annotations cover the safety profile, but with 0% schema description coverage and no output schema, the definition should say more about input format and return value. It leaves an agent to infer the result and edge-case 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 must compensate. It maps 'rectangle' to the range parameter and 'signed row and column offsets' to rows/cols, which is helpful, but it does not explain A1 notation, string format, or offset boundary behavior beyond what titles already show.

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 (shift/translate), resource (rectangle), and operation (signed row and column offsets while preserving shape). An agent can tell what it does, but the description does not differentiate it from siblings such as bpj_sheet_transpose_footprint or bpj_sheet_relative_position.

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 explains the operation but gives no explicit when-to-use conditions, prerequisites, or alternatives. An agent must infer that this is for moving a range without resizing, with no guidance on when to choose it over related sheet tools.

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.