Skip to main content
Glama

Separate header and body ranges

bpj_sheet_header_body
Read-onlyIdempotent

Divide a data rectangle at a requested header depth and report a null body when no rows remain.

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

Input Schema

NameRequiredDescriptionDefault
rangeYes
headerRowsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds one genuine behavioral detail not in the annotations: a null body is reported when no rows remain after the header. Beyond that edge case it says nothing about output shape or how headerRows interacts with range height.

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; every clause carries information. It is arguably too terse given the undocumented parameters, but nothing 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?

With no output schema and 0% parameter coverage, the description should clarify what the two returned pieces look like and how the range string is formatted. It hints at the null-body case but leaves the return structure and range syntax to inference, which is only minimally adequate for a 2-required-parameter tool.

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 carries the burden and only partially meets it: 'data rectangle' loosely maps to the range parameter and 'requested header depth' maps to headerRows. It never states the A1 notation requirement, the 160-character limit, or that headerRows must be at least 1, leaving the schema to speak for itself.

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 ('Divide') on a specific resource ('a data rectangle') and names the split axis ('requested header depth'), so an agent can tell it apart from geometry siblings like bpj_sheet_split_at_cell or bpj_sheet_intersection. It does not explicitly name any sibling, so it falls short of 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The use case is only implied: 'divide at a requested header depth' suggests header/body separation, but there is no statement of when to prefer this over alternatives such as bpj_sheet_split_at_cell or bpj_sheet_visible_ranges, and no exclusions or prerequisites.

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.