Skip to main content
Glama

Locate a cell within a selection

bpj_sheet_relative_position
Read-onlyIdempotent

Locate a selected cell by local row, local column and row-major sequence number inside a range.

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

Input Schema

NameRequiredDescriptionDefault
rangeYes
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 that the result includes local row, local column, and row-major sequence number, but it does not disclose behavior when the address is outside the range or otherwise invalid.

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?

It is a single front-loaded sentence with no filler. However, the phrase 'by local row, local column and row-major sequence number' can be misread as inputs rather than outputs, which slightly harms clarity.

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 two-parameter lookup tool with no output schema, the description is adequate but incomplete: it hints at return values yet omits address format and out-of-range behavior. Annotations cover the safety side, but the input semantics remain under-explained.

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, but it never explains the 'address' parameter and only vaguely references 'range'. The local row, local column, and sequence number phrasing describes likely outputs rather than clarifying how the two inputs should be formatted or interpreted.

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 ('Locate') and resource ('a selected cell') scoped 'inside a range', so the core operation is clear. It does not differentiate this from nearby siblings such as bpj_sheet_nth_cell or bpj_sheet_offset, leaving the agent to infer the distinction.

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 guidance on when to use this tool versus alternatives, nor any stated prerequisites such as the address needing to fall inside the supplied range. Usage is only implied by the phrase 'inside a range'.

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.