Skip to main content
Glama

Signature and blank-page count

bpj_design_signature_count
Read-onlyIdempotent

Plan full equal-sized signatures and identify the blank pages required at the end.

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>",
      "signature": "<signature>"
    },
    "name": "bpj_design_signature_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesYes
signatureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is fully covered by structured data. The description adds that blank pages are computed at the end of the run — useful behavioral context about what the result contains — but says nothing about how the result is reported (signature count, per-signature page ranges, blank page positions).

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 efficient sentence with the primary function front-loaded and no filler. It is arguably too terse for a two-parameter tool with zero schema description coverage, but nothing in it 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?

For a simple two-parameter arithmetic tool with annotations covering safety and no output schema, the description is minimally adequate. It still leaves the agent guessing about parameter meaning, the divisibility edge case, and the shape of the returned counts, which for a computation tool would be worth one extra clause.

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%; only bare titles exist, one of which carries the critical 'multiple of 4' constraint. The description mentions neither parameter and does not clarify whether 'pages' is the interior page count only or whether covers count, nor what happens when pages is not evenly divisible by the signature size.

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 names a specific verb+resource pair ('Plan full equal-sized signatures') and adds a second concrete output ('identify the blank pages required at the end'). It is clearly a print-imposition calculation, distinct from sibling design tools like bpj_design_bleed_canvas, though it never explicitly contrasts itself with any sibling.

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 or when-not-to-use guidance, no prerequisite (e.g. page count should include covers or not), and no mention of alternatives. The only usage signal is implicit in the word 'Plan', leaving the agent to infer that this is a pre-press imposition step.

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.