Skip to main content
Glama

The Doll Scout Home Tools

Estimate sheet supply · Shelf liners from sheets

tds_acid_free_shelf_liners
Read-onlyIdempotent

Count rectangular pieces per sheet and reserve extra pieces before rounding up. Shelf liners from sheets. Extra shelf liners for replacements.

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>",
      "extraShelfLiners": "<extraShelfLiners>"
    },
    "name": "tds_acid_free_shelf_liners"
  }
}

Input Schema

NameRequiredDescriptionDefault
cutSpacingMmYes
pieceWidthMmYes
piecesNeededYes
sheetWidthMmYes
pieceLengthMmYes
sheetLengthMmYes
extraShelfLinersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world, and non-destructive behavior. The description adds useful calculation behavior—reserving extra pieces before rounding up—but does not explain the return value, rounding outcome, or how cut spacing affects the estimate.

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?

The description is short and front-loads the core calculation. The fragments 'Shelf liners from sheets' and 'Extra shelf liners for replacements' are somewhat redundant but still provide domain context without bloat.

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 7-parameter calculation tool with zero schema descriptions and no output schema, the description is materially incomplete. It does not explain parameter meanings, units, output format, or edge conditions needed to invoke the tool 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% for 7 required parameters. The description only vaguely maps to sheet/piece dimensions and extra pieces, and never mentions 'cutSpacingMm' or clarifies units, layout, or how the extra parameter interacts with rounding.

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 first sentence states a specific calculation: 'Count rectangular pieces per sheet and reserve extra pieces before rounding up.' Combined with the title/name, it clearly identifies a sheet-supply estimator for shelf liners, though it does not explicitly differentiate itself from sibling shelf tools.

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?

The description provides no explicit when-to-use guidance, prerequisites, exclusions, or alternatives. Usage is only implied by the shelf-liner domain and the calculation wording.

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.