Skip to main content
Glama

Fabric pre-shrink cut

bpj_material_fabric_shrink_cut
Read-onlyIdempotent

Calculate fabric cutting dimensions for a target washed size using independent warp and weft shrinkage.

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": {
      "targetW": "<targetW>",
      "targetL": "<targetL>",
      "shrinkW": "<shrinkW>",
      "shrinkL": "<shrinkL>"
    },
    "name": "bpj_material_fabric_shrink_cut"
  }
}

Input Schema

NameRequiredDescriptionDefault
shrinkLYes
shrinkWYes
targetLYes
targetWYes

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description contributes the genuinely useful behavioral point that warp and weft shrinkage are treated independently, but it omits the formula, rounding behavior, and what the returned cutting dimensions look like.

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, front-loaded sentence with no filler; the purpose and the key mechanism come first. It packs a lot into one clause, but that is efficiency rather than padding.

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 four-required-parameter pure calculator with annotations covering safety, the description is adequate but thin: it never states the output shape (presumably a pair of cut width/length values) or the formula direction, which an agent needs to trust the result. No output schema exists to offload that.

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 carry the load. It does clarify the mapping that length corresponds to warp and width to weft shrinkage (matching the schema titles), and that the two axes are independent, but it leaves the actual relationship between target size and shrinkage percentage (cut = target/(1-shrink) versus target*(1+shrink)) and units unspecified.

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 ('Calculate') and resource ('fabric cutting dimensions'), and states the input framing ('target washed size') and the mechanism ('independent warp and weft shrinkage'). It is clearly distinguishable from the many material-estimation siblings, though it does not name any alternative explicitly.

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. The phrase 'target washed size' implies a scenario but an agent gets no instruction on when this calculation is appropriate versus e.g. bpj_material_shrinkage_fill or bpj_material_crosscut_stock.

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.