Skip to main content
Glama

The Doll Scout Home Tools

Plan packing carton quantities · Separately wrapped ornaments

tds_ornament_carton_run
Read-onlyIdempotent

Calculate identical-item grid capacity and cartons needed with a reserved slot allowance. Separately wrapped ornaments. Spaces occupied by dividers.

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": {
      "insideLengthMm": "<insideLengthMm>",
      "insideWidthMm": "<insideWidthMm>",
      "insideHeightMm": "<insideHeightMm>",
      "packedLengthMm": "<packedLengthMm>",
      "packedWidthMm": "<packedWidthMm>",
      "packedHeightMm": "<packedHeightMm>",
      "itemsToPack": "<itemsToPack>",
      "dividerSlots": "<dividerSlots>"
    },
    "name": "tds_ornament_carton_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsToPackYes
dividerSlotsYes
insideWidthMmYes
packedWidthMmYes
insideHeightMmYes
insideLengthMmYes
packedHeightMmYes
packedLengthMmYes

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 adds domain behavior beyond that: a reserved slot allowance and the fact that divider-occupied spaces reduce usable capacity, which materially affect the computed result. It omits whether dividers are subtracted from inside volume before or after grid fitting, and gives no sense of the returned quantities.

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?

Three short sentences with no filler, which is appropriately sized for the tool. But the second and third are verbless fragments that lack a subject or verb, so brevity comes at the cost of parseability rather than being genuinely front-loaded information.

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 eight mandatory parameters, zero schema descriptions, and no output schema, the description needs to explain the inputs and the shape of the calculation. Instead it leaves the dimension pairing, unit assumptions, and divider-slot arithmetic unexplained, so an agent cannot reliably populate the schema from the text alone.

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 eight required integer parameters, so the description must carry the semantic load and does not. It never explains the insideLengthMm/insideWidthMm/insideHeightMm versus packedLengthMm/packedWidthMm/packedHeightMm distinction (presumably container internal dimensions versus item dimensions including wrapping), nor the unit convention or how dividerSlots interacts with itemsToPack; only "dividers" loosely gestures at dividerSlots.

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 opening clause gives a concrete verb and resource ("Calculate identical-item grid capacity and cartons needed"), which is more than a restatement of the name. However, the two trailing fragments ("Separately wrapped ornaments." and "Spaces occupied by dividers.") are elliptical and could be read as scope conditions, inputs, or assumptions, so the exact problem solved stays fuzzy and no sibling tool is named to contrast against.

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 call this versus adjacent planning tools (framing plans, divider stock, portfolio pack runs), and no prerequisites or exclusions. The phrase "separately wrapped ornaments" hints at a material scenario but never says to choose this tool when items are individually wrapped and a different one otherwise.

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.