Skip to main content
Glama

The Doll Scout Home Tools

Reconcile item counts · Display shelf slots

tds_slot_id_stocktake
Read-onlyIdempotent

Compare two bounded lists on exact line IDs and show shortages, extras and repeat scans. Display shelf slots. Tolerated discrepancy per slot.

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": {
      "expectedIds": "<expectedIds>",
      "countedIds": "<countedIds>",
      "slotDiscrepancyLimit": "<slotDiscrepancyLimit>"
    },
    "name": "tds_slot_id_stocktake"
  }
}

Input Schema

NameRequiredDescriptionDefault
countedIdsYes
expectedIdsYes
slotDiscrepancyLimitYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover safety (readOnly, idempotent, closed-world, non-destructive), and the description adds real behavior: comparison is on exact line IDs, inputs are bounded, and the result reports shortages, extras and repeat scans. The remaining gap is how the per-slot tolerance is applied relative to the whole-slot comparison.

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?

Short and front-loads the comparison action and its outputs. The standalone fragment "Display shelf slots." and "Tolerated discrepancy per slot." are telegraphic and spend words without adding precision.

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?

For a three-required-parameter tool with no output schema and zero schema descriptions, the definition covers what is compared and roughly what comes back. It stops short of the input encoding format and the tolerance semantics, which an agent needs to call it correctly.

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?

With 0% schema coverage the description must carry the load, and it does partially: it maps the two inputs to line-ID lists and explains slotDiscrepancyLimit as a tolerated per-slot discrepancy. It never specifies how the bounded list strings are encoded (delimiter, line breaks), which matters for two 1600-character string parameters.

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 concrete action ("Compare two bounded lists on exact line IDs") and the domain (display shelf slots), with the reported outputs named. It is distinguishable from inventory-adjacent siblings, though "Display shelf slots" reads as a label rather than a scoping statement.

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?

No guidance on when to run a stocktake versus the many sibling stocktake tools, no prerequisites (e.g., when a count session exists), and no exclusions. The agent must infer applicability purely from the display-shelf framing.

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.