Skip to main content
Glama

Plan print pages with repeated headers

bpj_sheet_print_pages
Read-onlyIdempotent

Reserve room for repeated header rows on each page and report separate header and body ranges for each page.

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>",
      "width": "<width>",
      "headers": "<headers>"
    },
    "name": "bpj_sheet_print_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYes
widthYes
heightYes
headersYes

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description usefully adds that the output is split into header and body ranges per page, which no schema or annotation states, but it omits ordering of those ranges, how a partial trailing page is reported, or whether header rows consume the height budget.

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 tight sentence with the core concept front-loaded and no filler. It could be sharpened slightly, but nothing is wasted and it is easy to scan.

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 four-parameter tool with no output schema and no schema descriptions, the definition is thin: it never explains the parameter interplay or the shape and ordering of the returned page ranges. An agent can guess the intent but not confidently call it correctly in edge cases.

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% and the schema gives only bare titles, so the description carries the full burden of explaining the four required parameters. It does not clarify whether the height row count includes or excludes the repeated header rows, nor how range, width, and height interact at boundaries, leaving the most consequential ambiguity unresolved.

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?

Names a specific operation and resource: planning print page splits of a sheet while reserving rows for repeated headers, and it says it reports separate header and body ranges per page. That is concrete enough to distinguish it from generic range tools like bpj_sheet_qualify_range or bpj_sheet_header_body, though it does not explicitly name any sibling to contrast with.

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?

The description describes behavior, not when to reach for this tool versus alternatives. There is no statement of prerequisites, no exclusions, and no pointer to a sibling for the non-header-paginated case, so an agent must infer the print-planning use case from the title alone.

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.