Skip to main content
Glama

The Doll Scout Home Tools

Compare three handoff scans · Storage totes

tds_handoff_warehouse_totes
Read-onlyIdempotent

Match planned, departure and arrival IDs, then report units absent at each handoff. Storage totes. Totes scanned into storage.

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": {
      "plannedIds": "<plannedIds>",
      "departureIds": "<departureIds>",
      "warehouseArrivalIds": "<warehouseArrivalIds>"
    },
    "name": "tds_handoff_warehouse_totes"
  }
}

Input Schema

NameRequiredDescriptionDefault
plannedIdsYes
departureIdsYes
warehouseArrivalIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the comparison behavior itself — three-way match then absence reporting — but says nothing about how asymmetric or duplicate IDs across the three lists are treated, and there is no output schema to fall back on.

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?

The first sentence is front-loaded and earns its place. The trailing fragments 'Storage totes. Totes scanned into storage.' are redundant with each other and with the title, adding domain context at the cost of noise.

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?

Three required parameters with zero schema documentation and no output schema means the description must explain both input encoding and the shape of the absence report; it explains neither. For a three-way comparison tool whose result is the whole point, this leaves an agent guessing at how to format IDs and what it will receive back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the burden, and 'planned, departure and arrival IDs' at least maps each required string to the stage of the handoff it represents. It does not disclose the encoding of those strings despite 1600/2600-char limits strongly suggesting delimited ID lists, which is the main practical gap for a caller.

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?

States a specific verb-and-resource: match three sets of handoff IDs and report units absent at each handoff. The 'Storage totes' fragment identifies the resource domain, which separates it from the many sibling tds_handoff_* tools covering binders, props, fair stock and cartons. It stops short of explaining what a 'unit absent at each handoff' means in output terms.

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 and no named alternative or exclusion, even though siblings such as tds_paired_totes_stocktake and tds_threshold_storage_totes plausibly overlap on tote reconciliation. The precondition that all three scans must already exist is only implied by the required inputs.

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.