Skip to main content
Glama

The Doll Scout Home Tools

Estimate sheet supply · Rectangular packing dividers

tds_packing_divider_stock
Read-onlyIdempotent

Count rectangular pieces per sheet and reserve extra pieces before rounding up. Rectangular packing dividers. Spare dividers for fitting.

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>",
      "dividerSamplePieces": "<dividerSamplePieces>"
    },
    "name": "tds_packing_divider_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
cutSpacingMmYes
pieceWidthMmYes
piecesNeededYes
sheetWidthMmYes
pieceLengthMmYes
sheetLengthMmYes
dividerSamplePiecesYes

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, destructiveHint=false, and openWorldHint=false, so safety behavior is covered. The description adds that extra pieces are reserved before rounding up, but it does not explain the reserve rule, whether the result is an estimate, or how rounding interacts with the required parameters.

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

Conciseness3/5

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

The description is short and front-loads the main action, but the trailing fragments "Rectangular packing dividers. Spare dividers for fitting." are repetitive and add little clarity.

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?

For a computational tool with seven required parameters and no output schema, the description is incomplete. It does not explain parameter meanings, units, or the expected result format, leaving an agent unable to invoke it confidently.

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 seven required parameters, so the description must carry the burden. It offers only loose noun hints ("rectangular pieces", "sheet", "extra pieces") and does not explain units, constraints, or the meaning of parameters such as cutSpacingMm and dividerSamplePieces.

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 description gives a verb and resource ("Count rectangular pieces per sheet") and mentions reserving extra pieces before rounding up. However, the core operation is still ambiguous: "reserve extra pieces" and "Spare dividers for fitting" do not clearly explain what is being computed or returned, and no sibling alternative is named.

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 guidance on when to use this tool versus siblings such as tds_divider_reserve or tds_soft_figure_packing. No prerequisites, exclusions, or selection criteria are provided.

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.