Skip to main content
Glama

The Doll Scout Home Tools

Compare three handoff scans · Parcels transferred to pickup

tds_handoff_pickup_cabinet
Read-onlyIdempotent

Match planned, departure and arrival IDs, then report units absent at each handoff. Parcels transferred to pickup. IDs logged at pickup.

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>",
      "pickupReceiptIds": "<pickupReceiptIds>"
    },
    "name": "tds_handoff_pickup_cabinet"
  }
}

Input Schema

NameRequiredDescriptionDefault
plannedIdsYes
departureIdsYes
pickupReceiptIdsYes

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=true, idempotentHint=true, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds one genuinely useful behavioral fact — the result reports units absent at each handoff, i.e. it is a diff/comparison rather than a raw echo — but says nothing about mismatch handling, tolerance to duplicates, or what happens when the three ID sets differ in size.

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?

It is short, and the operative instruction is front-loaded. However, the two trailing sentence fragments about parcels and IDs logged at pickup add no actionable information and slightly muddle an otherwise single-sentence definition.

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?

There is no output schema, so the description is responsible for explaining the shape of the result; it only says units absent are reported, without saying per-handoff grouping or what is returned when nothing is missing. Combined with zero parameter documentation, an agent can invoke this tool but cannot confidently format inputs or interpret the response.

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 carries the full burden for three required parameters. It only loosely maps them (planned, departure, arrival/pickup) and gives no format guidance despite all three being length-capped strings (maxLength 1600/1600/2600), which strongly implies delimited ID lists whose delimiter and limit an agent cannot infer. The naming of the three roles is the only value added.

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 names a concrete operation: match planned, departure and arrival IDs and report units absent at each handoff. That is a real verb+resource, but it never distinguishes this tool from the many tds_handoff_* siblings, and the trailing fragments ("Parcels transferred to pickup. IDs logged at pickup.") read as restated labels rather than clarifying the purpose.

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 gives no when-to-use guidance, no prerequisites (e.g. that three scans of the same consignment are needed), and no indication of when another handoff tool is the better choice. An agent must infer the usage context entirely from the name and title.

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.