Skip to main content
Glama

Determine freeze-pane anchor

bpj_sheet_freeze_panes
Read-onlyIdempotent

Locate the first scrollable cell after freezing a requested number of leading rows and columns.

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": {
      "rows": "<rows>",
      "columns": "<columns>"
    },
    "name": "bpj_sheet_freeze_panes"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnsYes

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?

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful behavioral fact that this is a pure positional computation rather than a sheet mutation, but it says nothing about what is returned or how zero values behave.

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 well-formed sentence with no wasted words, and the operative concept (first scrollable cell) is stated up front. It is terse to the point of leaving gaps, but nothing in it is redundant.

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?

There is no output schema, so the description is the only place to explain what the tool returns, and it never specifies whether the result is a cell reference, coordinates, or an index. For a computational tool with two undocumented parameters, this is a material omission.

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 carry the parameter meaning, and it does partially by framing rows and columns as the leading rows/columns to be frozen. It does not explain the semantics of 0 (no freeze in that axis) or the upper bounds, so the compensation is incomplete.

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 concrete verb ('Locate') and a specific computed resource ('the first scrollable cell'), which usefully corrects the impression from the name that this tool actually freezes panes. It stops short of stating the output form (a cell address versus row/column indices) or differentiating it explicitly from siblings such as bpj_sheet_from_anchor.

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 phrase 'after freezing a requested number of leading rows and columns' implies the input context but never says when an agent should call this instead of an alternative, nor does it warn that the tool computes an anchor rather than applying a freeze. There are no exclusions or prerequisites.

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.