Skip to main content
Glama

The Doll Scout Home Tools

Estimate sheet supply · Price cards for display

tds_display_price_card_stock
Read-onlyIdempotent

Count rectangular pieces per sheet and reserve extra pieces before rounding up. Price cards for display. Blank cards to reserve.

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>",
      "blankCardsReserve": "<blankCardsReserve>"
    },
    "name": "tds_display_price_card_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
cutSpacingMmYes
pieceWidthMmYes
piecesNeededYes
sheetWidthMmYes
pieceLengthMmYes
sheetLengthMmYes
blankCardsReserveYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/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 adds only that results are rounded up with an extra-piece reserve; it says nothing about units, how the reserve interacts with piecesNeeded, or what the response contains.

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, but the three-sentence structure is fragmentary and the operational rule is buried behind a noun-phrase title restatement. Little is wasted, yet the ordering does not front-load what an agent most needs.

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?

A seven-parameter, all-required computation tool with no output schema needs far more explanation than three terse lines. The description leaves the arithmetic, unit conventions, and result shape entirely unstated.

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 sheet/piece dimensions, cut spacing, and a blank-card reserve, but never maps meaning onto named fields or clarifies units (mm) or the relationship between piecesNeeded and blankCardsReserve.

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?

"Count rectangular pieces per sheet and reserve extra pieces before rounding up" does convey a specific computation (sheet yield with a reserve and round-up). But the follow-on fragments "Price cards for display. Blank cards to reserve." read as domain tags rather than purpose, and nothing distinguishes this from siblings such as tds_unit_price_card_dividers or tds_break_even_card_lot.

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 statement, no prerequisite, and no named alternative among the many tds_*_stock/unit_price siblings. An agent must guess whether this is the right tool for a supply estimate versus a price or divider calculation.

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.