Skip to main content
Glama

The Doll Scout Home Tools

Compare three handoff scans · Moved cartons

tds_handoff_moving_cartons
Read-onlyIdempotent

Match planned, departure and arrival IDs, then report units absent at each handoff. Moved cartons. Carton IDs at the new address.

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>",
      "newHomeCartonIds": "<newHomeCartonIds>"
    },
    "name": "tds_handoff_moving_cartons"
  }
}

Input Schema

NameRequiredDescriptionDefault
plannedIdsYes
departureIdsYes
newHomeCartonIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/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 nothing beyond that — nothing about whether ID order matters, whether duplicates or missing entries are tolerated, or what the result looks like when all three lists agree.

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 operative sentence is compact and front-loaded, but it is followed by two fragmentary clauses ('Moved cartons.' and 'Carton IDs at the new address.') that read as titles or stray labels rather than information. The definition is short yet not efficient, since part of it does not earn its place.

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, fully undocumented parameters with no output schema and no param descriptions mean the description must carry the load, and it does not: input list encoding, what 'units absent' means in the response, and failure behavior when a list is empty are all unstated. For a comparison tool whose whole value is interpreting mismatched ID sets, this is materially incomplete.

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

Parameters3/5

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

Schema description coverage is 0% and all three parameters are required strings with large maxLengths (1600/1600/2600), which strongly implies delimiter-joined ID lists — yet the format is never stated. The description loosely maps the parameters to planned, departure and 'new address' carton IDs, giving partial semantic orientation, but it leaves the encoding of the inputs entirely to guesswork. That lands just below the baseline-3 case because the schema here is not doing the heavy lifting.

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 concrete operation — match planned, departure and arrival ID lists and report units missing at each handoff — which is a specific verb+resource an agent can act on. It does not distinguish itself from the many tds_handoff_* siblings, and the trailing fragments ('Moved cartons. Carton IDs at the new address.') blur rather than sharpen the purpose, but the core action is legible.

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 contains no when-to-use guidance, no prerequisites, and no mention of any alternative tool for this kind of reconciliation. An agent must infer entirely from the name and title that this is the carton-transfer variant of a handoff comparison.

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.