Skip to main content
Glama

Decode an A1 cell address

bpj_sheet_parse_cell
Read-onlyIdempotent

Decode one-based row and column coordinates and absolute-reference markers.

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>"
    },
    "name": "bpj_sheet_parse_cell"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds nothing beyond that: it does not say what happens with malformed or out-of-range addresses (the 160-char cap hints at limits), nor what the decoded result looks like, which matters because no output schema exists.

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 part of why key details are missing rather than a virtue in itself.

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?

With no output schema, the description carries the burden of explaining the return value (row, column, absolute flags, 1-based vs 0-based output) and it does not. For a pure decode/parse utility whose only value is its output shape, that is a substantial 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 coverage is 0% and only the schema title ('A1 cell address') and maxLength identify the parameter. The description contributes some meaning by implying absolute markers (e.g. $A$1) are accepted and that indexing is one-based, but it gives no format examples or concrete accepted syntax.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

'Decode' plus 'one-based row and column coordinates and absolute-reference markers' loosely points at A1-address parsing, but the direction of the transform is only pinned down by the title ('Decode an A1 cell address'), and the description does not name the inverse sibling bpj_sheet_compose_cell or any other neighbor. An agent can guess the purpose but the sentence itself is vague about what is decoded into what.

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 when-to-use statement, no mention of alternatives such as bpj_sheet_compose_cell (the inverse) or bpj_sheet_nth_cell, and no note on invalid-address behavior. The agent gets no routing guidance at all.

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.