Skip to main content
Glama

The Doll Scout Home Tools

Estimate sheet supply · Rectangular cloth separators

tds_cloth_separator_stock
Read-onlyIdempotent

Count rectangular pieces per sheet and reserve extra pieces before rounding up. Rectangular cloth separators. Extra cloth separators.

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": {
      "sheetWidthMm": "<sheetWidthMm>",
      "sheetLengthMm": "<sheetLengthMm>",
      "pieceWidthMm": "<pieceWidthMm>",
      "pieceLengthMm": "<pieceLengthMm>",
      "piecesNeeded": "<piecesNeeded>",
      "cutSpacingMm": "<cutSpacingMm>",
      "extraClothPieces": "<extraClothPieces>"
    },
    "name": "tds_cloth_separator_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
cutSpacingMmYes
pieceWidthMmYes
piecesNeededYes
sheetWidthMmYes
pieceLengthMmYes
sheetLengthMmYes
extraClothPiecesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description does add one piece of real behavioral context — that extra pieces are reserved before rounding up, which implies a ceiling-style computation — but it never says what the result contains (sheet count? piece count? surplus?), which is the main unknown for a calculator tool.

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

Conciseness2/5

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

Only three sentences, but two are redundant one-word-phrase restatements of the tool name and burn attention without adding information. The useful clause is buried mid-sentence rather than front-loaded as a clear purpose statement.

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 7-required-parameter computation tool with no output schema and no parameter documentation, the definition should at minimum explain the inputs and the shape of the answer. It covers neither, though the annotation set does relieve it of the safety/auth burden.

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% across 7 required parameters, so the description carries the full burden and largely fails. It gestures at 'pieces per sheet' and 'extra pieces' (extraClothPieces) but never explains cutSpacingMm at all, nor units (mm), nor the relationship between sheetWidthMm/sheetLengthMm and piece dimensions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence gives a recognizable operation (count pieces per sheet, add extra pieces, round up) applied to rectangular cloth separators, so the purpose is inferable. But the two trailing fragments ('Rectangular cloth separators. Extra cloth separators.') are keyword echoes rather than a specification, and nothing distinguishes this from siblings like tds_cloth_wraps_reserve or tds_packing_divider_stock.

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 statement of when to use this tool, when to prefer another, or any precondition. The agent must guess from the name alone whether this is the right estimator versus the other *_stock siblings.

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.