Skip to main content
Glama

The Doll Scout Home Tools

Compare three handoff scans · Sleeved cards

tds_handoff_tracked_sleeves
Read-onlyIdempotent

Match planned, departure and arrival IDs, then report units absent at each handoff. Sleeved cards. Sleeve IDs counted at arrival.

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>",
      "sleeveArrivalIds": "<sleeveArrivalIds>"
    },
    "name": "tds_handoff_tracked_sleeves"
  }
}

Input Schema

NameRequiredDescriptionDefault
plannedIdsYes
departureIdsYes
sleeveArrivalIdsYes

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, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds one genuinely useful behavioral rule — that sleeves, not the cards inside, are what get counted at arrival — but says nothing about how missing units are classified, whether partial or duplicate scans are tolerated, or what the report contains.

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?

Three short sentences, front-loaded with the operation before the scope qualifier. The sentence fragment "Sleeved cards." is terse but carries real disambiguating value; no filler or redundancy is present.

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?

For a read-only comparison tool with three all-required parameters at 0% schema coverage and no output schema, the description should specify the ID encoding and at least sketch the shape of the absence report. Neither is present, leaving the agent to guess the input format despite no output schema explaining the return.

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% and the description only loosely maps the three strings to planned/departure/arrival. It never explains the encoding: whether IDs are comma-, newline- or space-delimited, whether a single ID is allowed, or why sleeveArrivalIds has a larger maxLength (2600 vs 1600) — a detail an agent must get right to build a valid call.

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 description states specific verbs ("match", "report") against specific resources (planned, departure and arrival IDs) and names the outcome ("units absent at each handoff"). The qualifier "Sleeved cards" distinguishes it from the many sibling tds_handoff_* variants (binders, cartons, totes, props), though it never explicitly contrasts with any of them.

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 or when-not-to-use guidance, no statement of prerequisites (e.g. that all three scans must cover the same population or that scans must be in a particular order), and no alternative named. "Sleeved cards." functions as a scope label rather than usable invocation guidance.

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.