Skip to main content
Glama

The Doll Scout Home Tools

Plan packing carton quantities · Photo props packed for transit

tds_photo_prop_parcels
Read-onlyIdempotent

Calculate identical-item grid capacity and cartons needed with a reserved slot allowance. Photo props packed for transit. Spaces for location labels.

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>",
      "locationLabelSlots": "<locationLabelSlots>"
    },
    "name": "tds_photo_prop_parcels"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsToPackYes
insideWidthMmYes
packedWidthMmYes
insideHeightMmYes
insideLengthMmYes
packedHeightMmYes
packedLengthMmYes
locationLabelSlotsYes

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a little beyond that by introducing the 'reserved slot allowance' concept and implying label slots consume capacity, but it never says whether the result is a count, a layout, or how rounding/partial cartons are handled.

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?

It is short and the operative statement is front-loaded. The two trailing sentence fragments are grammatically incomplete and add ambiguity, but the overall length is not wasteful.

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?

This is a computation tool with 8 required numeric inputs, no output schema, and zero parameter documentation, yet the description does not explain the returned carton count or how the reserved-slot allowance affects it. An agent has enough to make the call but not enough to trust or interpret the result.

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 8 required parameters, so the description carries the full burden and fails to compensate. It never explains the inside-vs-packed dimension pairing, what itemsToPack vs locationLabelSlots do to the grid, or any unit or rounding conventions; 'Spaces for location labels' is the only faint gesture toward a parameter name.

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 names a specific verb and resource: 'Calculate identical-item grid capacity and cartons needed with a reserved slot allowance,' which tells an agent this is a packing/carton estimation computation, not a lookup or mutation. The trailing fragments ('Photo props packed for transit. Spaces for location labels.') muddy rather than sharpen the scope, and no sibling is named to contrast with, so it stops short of 5.

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, when-not-to-use, or alternative routing guidance at all. An agent cannot tell from this text whether to prefer it over siblings such as tds_packing_divider_stock or tds_threshold_carton_inserts, nor what preconditions apply.

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.