Skip to main content
Glama

Translate copied cell references

bpj_sheet_copy_reference
Read-onlyIdempotent

Translate an A1 reference on copy, respecting fixed row and column components.

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

Input Schema

NameRequiredDescriptionDefault
colsYes
rowsYes
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare this a safe, idempotent, non-destructive local read, so the safety profile is covered. The description contributes real behavioral value by stating that fixed row and column components are respected — the core algorithm. It does not address edge cases such as out-of-bounds offsets (schema caps at 16384/1048576), invalid addresses, or whether range references are handled, so it stops at a 3.

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 front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is also the source of the coverage gaps noted elsewhere.

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?

For a three-required-parameter tool with zero schema description coverage and no output schema, the description is too thin. It never explains what the returned value looks like (a translated address string), nor how rows/cols offsets are applied, leaving the agent to guess at the core contract.

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 the parameter burden. It clarifies that 'address' is an A1 reference with optional locks and that fixed ($) components are preserved, which is useful. However, the 'rows' and 'cols' offset parameters are never mentioned, so their units, sign convention, and effect are left entirely to the bare titles in the schema.

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 names a specific verb and resource: 'Translate an A1 reference on copy.' An agent can immediately tell this transforms one cell address into another. It stops short of differentiating itself from near neighbors such as bpj_sheet_offset or bpj_sheet_relative_position, so a 4 rather than a 5.

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?

'On copy' weakly implies the scenario (simulating what happens when a formula is copied), but there is no explicit when-to-use, when-not-to-use, or named alternative. With several sibling tools operating on sheet coordinates, the agent gets no routing signal.

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.