Skip to main content
Glama

The Doll Scout Home Tools

Compare three handoff scans · Stock transported to a fair

tds_handoff_fair_stock
Read-onlyIdempotent

Match planned, departure and arrival IDs, then report units absent at each handoff. Stock transported to a fair. Stock IDs scanned at the stall.

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>",
      "stallArrivalIds": "<stallArrivalIds>"
    },
    "name": "tds_handoff_fair_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
plannedIdsYes
departureIdsYes
stallArrivalIdsYes

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 openWorldHint=false, so safety and repeatability are covered structurally. The description adds the useful behavioral point that the tool performs cross-set matching and reports absences per handoff stage, which the annotations do not convey. It stops short of disclosing matching rules, tolerance for missing stages, or what the report looks like.

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 opening sentence is well-formed and front-loaded with the verb and result. The two trailing fragments, 'Stock transported to a fair.' and 'Stock IDs scanned at the stall.', largely duplicate the title's context and add no operational detail, so they dilute rather than inform.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, 0% schema coverage and three required parameters, the description should do more: it names the returned concept (units absent at each handoff) but never specifies the ID list format or the shape of the per-handoff report. It is sufficient to understand the intent but not fully sufficient to invoke the tool correctly on the first attempt.

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 parameter meaning and largely does not. It maps the three required inputs to planned, departure and arrival scans, but each is a plain string (maxLength 1600/1600/2600), and nothing explains the encoding of multiple IDs — delimiter, whitespace handling, deduplication — or why the arrival field is longer.

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 operation on a specific resource: match planned/departure/arrival ID sets and report units absent at each handoff. This is far more than a restatement of the name. It does not, however, distinguish itself from the many sibling tds_handoff_* tools, so an agent cannot tell from the text alone why it would pick this one over tds_handoff_lent_art or tds_handoff_packaging_station.

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 and no named alternative. The fragments 'Stock transported to a fair' and 'Stock IDs scanned at the stall' hint at a scenario but give no condition for selecting this tool over a sibling handoff tool, nor any prerequisite such as needing all three scans to exist first.

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.