Skip to main content
Glama

Compose a cell address from coordinates

bpj_sheet_compose_cell
Read-onlyIdempotent

Encode numeric worksheet coordinates in A1 and absolute R1C1 notation.

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": {
      "row": "<row>",
      "column": "<column>"
    },
    "name": "bpj_sheet_compose_cell"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value by disclosing the output notations even though no output schema exists, but it leaves ambiguity about whether one or both notations are returned and whether the R1C1 form includes absolute markers (R1C1 vs R[1]C[1]).

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 short sentence with no filler, and the action is front-loaded. The brevity borders on under-specification rather than padding, but nothing in the sentence is wasted.

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 pure function with strong annotations, most of what an agent needs is present. The remaining gap is the return shape: whether the reply is a single concatenated string, a pair of notations, or which exact syntax ('$A$1' vs 'A1', 'R1C1' vs 'R[1]C[1]') is emitted.

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 meaning; it frames both parameters as 1-based numeric worksheet coordinates, which aligns with the schema's minimum of 1 and the 1048576/16384 bounds. However, it adds no detail on ordering, units, or what happens at boundary values, so compensation is only partial.

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 a specific verb ('Encode') over a specific input ('numeric worksheet coordinates') and names the produced artifacts (A1 and absolute R1C1 notation), so an agent knows exactly what the tool yields. It falls short of 5 only because it does not differentiate itself from the closely related siblings such as bpj_sheet_parse_cell (the inverse) or bpj_sheet_nth_cell.

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 or when-not-to-use guidance and no named alternative. An agent must infer from the verb alone that this is the coordinate-to-address direction, and must guess that bpj_sheet_parse_cell handles the reverse conversion.

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.