Skip to main content
Glama

Saddle-stitch folio pairs

bpj_design_saddle_folio
Read-onlyIdempotent

Return front and back printer’s pairs for the chosen folded sheet counted from the outside; padded pages are blank.

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": {
      "pages": "<pages>",
      "sheet": "<sheet>"
    },
    "name": "bpj_design_saddle_folio"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesYes
sheetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds two useful behavioral details—padded pages are blank and the sheet is counted from the outside—but it does not describe the return structure (e.g., how front/back pairs are formatted) or error conditions, leaving meaningful gaps beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. Every clause carries information about the output (front and back printer's pairs), the input context (chosen folded sheet counted from the outside), and edge-case behavior (padded pages are blank).

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 two required parameters, no output schema, and annotations covering safety, the description is adequate but incomplete. It explains what is returned in broad terms but not the shape of the return value (list of pairs? objects?), and it omits constraints such as whether 'pages' must be a multiple of four for a valid saddle-stitch imposition.

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. It clarifies that 'sheet' is counted from the outside and that padded pages are blank, which adds some meaning beyond the schema titles. However, it does not explain what 'pages' represents precisely (total interior pages? must it be a multiple of 4?) or how the two parameters interact, so compensation is only partial.

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 ('Return') and resource ('front and back printer's pairs for the chosen folded sheet'), making the core action clear. It does not explicitly differentiate from sibling design tools, but the name and title already signal a saddle-stitch imposition function distinct from the many statistical 'pairs' 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?

The description gives no when-to-use guidance, no prerequisites, and no alternatives. It implies the tool is for saddle-stitch folio pair generation but never states when to choose it over other design or pairs tools, leaving the agent to infer from the name 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.