Skip to main content
Glama

Preview a transposed paste footprint

bpj_sheet_transpose_footprint
Read-onlyIdempotent

Swap the source dimensions and report the footprint of a transposed paste at the destination cell.

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_transpose_footprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYes
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds that this is a computational preview rather than a mutation, but it does not describe validation, error behavior, or what 'footprint' means as a result.

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?

The definition is a single front-loaded sentence with no wasted wording. Its brevity contributes to the missing guidance, but structurally it is clean and easy to parse.

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?

No output schema exists, so the description must explain what 'footprint' is returned; it only says 'report the footprint' without stating whether that is dimensions, a range, a cell count, or another shape. Combined with 0% parameter description coverage, this leaves too much for an agent to infer.

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%; the schema only supplies titles such as 'A1 rectangular range' and 'A1 cell address'. The description partially compensates by implying the range provides the source dimensions and the address is the destination cell, but it does not explicitly map those terms to the parameter names or clarify the destination-cell anchoring.

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 uses specific verbs ('swap', 'report') and a specific resource ('footprint of a transposed paste at the destination cell'), so an agent can distinguish this from value-level transpose or generic dimension tools. It does not explicitly name a sibling alternative, but the purpose is clear.

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 explicit when-to-use guidance, no prerequisites, and no alternatives named. A reader can infer it is for previewing a transposed paste footprint, but nothing says when to choose it over bpj_matrix_transpose or sheet dimension 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.