Skip to main content
Glama

Print stock batch weight

bpj_design_stock_batch_weight
Read-onlyIdempotent

Estimate bare stock weight from sheet dimensions, grammage, and sheet quantity.

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": {
      "width": "<width>",
      "height": "<height>",
      "grammage": "<grammage>",
      "sheets": "<sheets>"
    },
    "name": "bpj_design_stock_batch_weight"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthYes
heightYes
sheetsYes
grammageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds two genuinely useful behavioral cues beyond that: "Estimate" signals an approximation, and "bare" signals paper stock only, excluding ink, wrap or pallet weight. It stops short of stating the output unit (kg vs g), rounding, or whether trim waste is included, which are the behaviors an agent would still need.

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?

One front-loaded sentence with zero filler; the computation and its inputs come first. It is efficient, though for a tool with four required numeric inputs and no output schema it is arguably thinner than the task warrants rather than padded.

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 closed-world calculator with rich annotations and no output schema, most of what an agent needs is present. The gaps are the return unit and the calculation's assumptions (bare stock only, no waste allowance), which matter for interpreting the number even on a tool this small.

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%, but the schema titles carry units (Trim width mm, Trim height mm, Grammage g/m2, Sheet count), so the raw unit information is not lost. The description maps all four inputs in a readable grouping ("sheet dimensions, grammage, and sheet quantity") but adds no semantics of its own — notably it says "sheet dimensions" while the schema says "Trim" width/height, an unresolved trim-vs-sheet distinction.

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 ("Estimate") and a precise resource ("bare stock weight") plus the three input families that produce it, so the agent knows exactly what computation happens. It does not explicitly contrast itself with near-siblings such as bpj_carrier_billable_weight or bpj_material_crosscut_stock, so sibling differentiation is left to the "bare stock" qualifier rather than stated.

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, when-not-to-use, or alternative-tool guidance anywhere in the description. The agent must infer from the phrase "bare stock weight" that this is the paper-only estimate rather than billable/shipping weight, which is a real ambiguity given siblings about carrier billable weight and freight allocation.

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.