Skip to main content
Glama

Equal crosscuts with kerf

bpj_material_crosscut_stock
Read-onlyIdempotent

Plan equal cutoffs when each cut piece consumes one kerf, with no end trimming allowance.

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": {
      "stock": "<stock>",
      "piece": "<piece>",
      "kerf": "<kerf>",
      "quantity": "<quantity>"
    },
    "name": "bpj_material_crosscut_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
kerfYes
pieceYes
stockYes
quantityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so safety is covered. The description adds genuinely useful behavioral specifics beyond that: exactly one kerf is charged per cut piece (not per cut, not at the ends) and no end-trim allowance is applied, which are the assumptions that determine the arithmetic. It still says nothing about what the result contains (piece count vs. leftover vs. required stock), but for a pure computation the modeling disclosure is the more important gap to close.

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; the modeling constraint is stated before anything else. Nothing in it is redundant with the name or title.

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?

There is no output schema, four required parameters with zero description coverage, and no statement of what is returned or how quantity drives the result. For a calculator whose entire value is its output (pieces per stock, leftover, stock required), the description leaves the agent guessing at the contract even though the domain model is well stated.

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 all four parameters are undocumented beyond short titles, so the description must compensate and largely does not. It clarifies the kerf and cut-length relationship implicitly, but leaves the crucial ambiguity of 'quantity' unresolved — whether it is the number of pieces desired or the number of stock lengths, and correspondingly what the tool optimizes. The stock-vs-piece relationship is only inferable.

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 gives a specific verb ('Plan') and resource ('equal cutoffs') drawn from a stock length, and it pins down the cutting model. An agent can tell this is a crosscut/layout calculation rather than, say, a board-feet or shrinkage calculation. It does not name or contrast any sibling explicitly, so it stops 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 clause 'when each cut piece consumes one kerf, with no end trimming allowance' defines the modeling condition under which the tool is valid, which is real usage guidance. However, there is no guidance on when to prefer an alternative tool (e.g. a shrink-cut or sheet-layout sibling) and no statement of when this model would give wrong answers.

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.