Skip to main content
Glama

Predict appended row footprint

bpj_sheet_append_location
Read-onlyIdempotent

Determine where appended rows will land and report the resulting expanded selection.

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

Input Schema

NameRequiredDescriptionDefault
rangeYes
heightYes

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds that the operation predicts rather than performs an append and produces a resulting selection, which is consistent with the annotations and mildly useful. It does not say what the returned selection contains, whether the input range is modified, or how the footprint is computed.

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 and no repetition of the name or title. It is efficient, though its brevity comes partly from omitting the parameter and return-value detail an agent needs.

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?

There is no output schema, so the description should explain what the 'resulting expanded selection' looks like and how the two inputs map to it; it does neither. For a two-parameter tool with zero schema description coverage, the definition leaves an agent guessing about input meaning and return shape.

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 carries the full burden, yet it never mentions either parameter. It implies that 'height' is the number of appended rows and that 'range' is the anchor area, but neither is stated explicitly, nor is whether the range is modified or only measured. The schema supplies only titles and bounds, so a real gap remains.

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 states a specific verb and resource: determine where appended rows will land, and report the resulting expanded selection. That is enough for an agent to understand this is a prediction/computation over a sheet range rather than a mutation. It does not, however, distinguish the tool from similar footprint siblings such as bpj_sheet_transpose_footprint or bpj_sheet_bounding_box, and 'expanded selection' stays undefined.

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 guidance, no prerequisites, and no exclusions or alternatives. The agent must infer from the name and title alone that this is the right call when it needs to know where appended rows would land. Nothing states how this differs from other footprint tools in the catalog.

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.