Skip to main content
Glama

The Doll Scout Home Tools

Compare three handoff scans · Collections moved into archive

tds_handoff_archival_binders
Read-onlyIdempotent

Match planned, departure and arrival IDs, then report units absent at each handoff. Collections moved into archive. Archive arrival identifiers.

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>",
      "archiveScanIds": "<archiveScanIds>"
    },
    "name": "tds_handoff_archival_binders"
  }
}

Input Schema

NameRequiredDescriptionDefault
plannedIdsYes
departureIdsYes
archiveScanIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/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 fully covered without the description. The description does add one piece of genuine behavioral value: the tool compares the three inputs and reports units missing per handoff, which is more than the annotations convey. It says nothing about the format of the report or how unmatched IDs 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.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the operation, but two of the three sentences are dangling fragments ("Collections moved into archive. Archive arrival identifiers.") whose meaning is unclear and which consume space without informing the caller. Terseness here reads as under-specification rather than efficiency.

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 no output schema, the description is the only place to explain what comes back, and 'report units absent at each handoff' is only a partial account of the result shape. Combined with the unexplained string encoding of the three required ID parameters, an agent cannot confidently construct a call from this definition 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%, so the description must carry the burden, and it only loosely maps the three inputs to 'planned, departure and arrival' without stating their format. The maxLength values (1600, 1600, 2600) strongly imply delimited ID lists rather than single IDs, but neither the schema nor the description explains the delimiter or encoding, leaving a real risk of malformed calls.

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 first sentence gives a reasonably specific operation: match three ID sets (planned, departure, arrival) and report units absent at each handoff. However, the trailing fragments "Collections moved into archive. Archive arrival identifiers." are noun phrases with no verb and add no discriminating information. Nothing distinguishes this from the many other tds_handoff_* siblings.

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 use this tool versus the numerous handoff siblings (tds_handoff_tracked_sleeves, tds_handoff_warehouse_totes, etc.), nor any prerequisite such as the scans needing to be from the same shipment. The agent must infer the use case entirely from the name and the one operational sentence.

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.