Skip to main content
Glama

The Doll Scout Home Tools

Reconcile item counts · Closed storage totes

tds_paired_totes_stocktake
Read-onlyIdempotent

Compare two bounded lists on exact line IDs and show shortages, extras and repeat scans. Closed storage totes. Tolerated variance per tote ID.

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>",
      "closedToteTolerance": "<closedToteTolerance>"
    },
    "name": "tds_paired_totes_stocktake"
  }
}

Input Schema

NameRequiredDescriptionDefault
countedIdsYes
expectedIdsYes
closedToteToleranceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, closed-world read. The description adds genuine behavior beyond them: matching is on exact line IDs (not fuzzy), and the output is a three-way classification of shortages, extras and repeat scans. It does not explain how tolerance changes the reported results or what 'repeat scans' look like in the output.

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, front-loaded sentences with no padding; the core comparison behavior leads. 'Closed storage totes.' reads as a bare tag rather than a sentence, which costs a bit of clarity.

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 read-only comparison tool with no output schema, the description covers what is compared and roughly what is returned. It leaves the two highest-risk unknowns unexplained: the delimiter/format of the ID lists and the units and effect of the tolerance value.

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 all meaning. It hints that expectedIds and countedIds are lists of line IDs and that tolerance is per tote ID, but never states the list encoding for the two 1600-character strings or whether closedToteTolerance is a count or a percentage — the two things an agent most needs.

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 verb and resource: compare two bounded lists on exact line IDs and report shortages, extras and repeat scans. That is far more specific than the title's 'reconcile item counts', though it never names a distinguishing sibling among the many stocktake tools.

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 comparison framing implies when the tool applies (reconciling a physical count against an expected list), but there is no explicit when-to-use statement, no exclusions, and no pointer to the many sibling stocktake tools that presumably handle other containers.

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.