Skip to main content
Glama

Qualify an address with a worksheet name

bpj_sheet_qualify_range
Read-onlyIdempotent

Quote the worksheet name, escape embedded apostrophes and attach a normalized 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>",
      "name": "<name>"
    },
    "name": "bpj_sheet_qualify_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
rangeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

The annotations already establish that this is a safe, idempotent, closed-world read operation. The description adds useful behavioral detail by saying the worksheet name is quoted and embedded apostrophes are escaped, and that the range is normalized. It still does not define the normalization rules or the exact output shape, but the annotations carry the safety profile.

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?

The definition is a single compact sentence with no redundant wording, and it front-loads the three concrete operations. It is terse enough to scan quickly, though the lack of a stated result makes it slightly less effective than a fully front-loaded purpose statement.

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 two-parameter string-construction tool with no output schema, the description should state what is returned and clarify normalization and escaping behavior. It gives the transformation steps but omits the return value, examples, and validation behavior. This leaves meaningful gaps for correct invocation and interpretation of results.

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 compensate for the two undocumented parameters. It clarifies that the worksheet name is quoted and apostrophe-escaped, and that the range is normalized, which adds meaning beyond the bare schema titles. However, 'normalized range' is left undefined and the expected A1 format is only implied by the schema title.

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?

The description lists concrete transformations—quoting the worksheet name, escaping apostrophes, and attaching a normalized range—but never explicitly states that the tool returns a fully qualified sheet-range reference. The verb 'qualify' in the tool name and title is uncommon enough that an agent must infer the result from the described steps. It is adequate but not sharply differentiated from related sheet-reference tools.

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 guidance on when to use this tool versus alternatives, nor any stated preconditions or exclusions. The description only describes internal string transformations, leaving the agent to infer that this is for building a sheet-qualified range reference. No when-not-to-use information is provided.

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.