Skip to main content
Glama

The Doll Scout Home Tools

Estimate sheet supply · Drawer protection film

tds_drawer_insert_film
Read-onlyIdempotent

Count rectangular pieces per sheet and reserve extra pieces before rounding up. Drawer protection film. Pieces for edge 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>",
      "edgeTestPieces": "<edgeTestPieces>"
    },
    "name": "tds_drawer_insert_film"
  }
}

Input Schema

NameRequiredDescriptionDefault
cutSpacingMmYes
pieceWidthMmYes
piecesNeededYes
sheetWidthMmYes
pieceLengthMmYes
sheetLengthMmYes
edgeTestPiecesYes

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 safety is covered. The description adds one genuinely useful behavioral fact — that extra pieces are reserved before rounding up, i.e. results are padded upward — but says nothing about what is returned (pieces per sheet vs. sheets required) or how the edge-test reservation interacts with the count.

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?

It is short and front-loaded with the core computation, so there is no padding to trim. However, the two trailing sentence fragments are cryptic labels rather than informative clauses, so the brevity comes at the cost of clarity rather than from discipline.

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?

With 7 required inputs, no output schema, and no parameter descriptions, the definition is under-specified: an agent cannot tell what the tool returns or what units and constraints apply to cut spacing and edge-test pieces. The annotations cover the safety profile but not the computational contract.

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 never states units (mm), never explains cutSpacingMm as the gap/kerf between pieces, and only obliquely gestures at edgeTestPieces with 'pieces for edge fitting'. The self-describing parameter names provide the only real semantics.

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 does name a verb and outcome ('Count rectangular pieces per sheet and reserve extra pieces before rounding up'), but the following fragments ('Drawer protection film. Pieces for edge fitting.') read as tags rather than a purpose statement, and nothing distinguishes this sheet-counting tool from siblings like tds_condition_sheet_index or tds_photo_table_insert_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 when-to-use guidance at all: no condition that selects this tool over the other drawer/sheet siblings, no prerequisites, and no statement of what it should not be used for. The agent must infer applicability purely from the name.

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.