Skip to main content
Glama

The Doll Scout Home Tools

Reconcile item counts · Market table stock

tds_event_kit_stocktake
Read-onlyIdempotent

Compare two bounded lists on exact line IDs and show shortages, extras and repeat scans. Market table stock. Tolerated variance per table stock 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>",
      "tableIdTolerance": "<tableIdTolerance>"
    },
    "name": "tds_event_kit_stocktake"
  }
}

Input Schema

NameRequiredDescriptionDefault
countedIdsYes
expectedIdsYes
tableIdToleranceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavioral detail beyond that: matching is on exact line IDs, and results include shortages, extras and repeat scans. It stops short of explaining how the two lists are encoded as strings or what a tolerance breach does to 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentence is front-loaded and efficient, but the two trailing fragments ('Market table stock.' 'Tolerated variance per table stock ID.') are telegraphic and read like truncated metadata rather than informative text. Overall it is short, but not all of it earns 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?

With no output schema and zero schema description coverage, the description carries the full documentation burden for a 3-required-parameter tool. It names the reported categories but omits the string encoding of the ID lists, the meaning of the tolerance value, and any indication of ordering or duplicate handling, leaving real ambiguity before invocation.

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% for all three required parameters, so the description must compensate. It only partially does: 'exact line IDs' gestures at expectedIds/countedIds, but neither parameter is named, and the critical fact that each is a single string (maxLength 1600, presumably delimited) is never stated. 'Tolerated variance per table stock ID' loosely maps to tableIdTolerance but gives no units or effect.

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 (compare two bounded lists on exact line IDs) and names the outputs (shortages, extras, repeat scans), so an agent can tell this is a reconciliation/stocktake diff tool. It does not differentiate itself from the many sibling '*_stocktake' tools, and the trailing fragment 'Market table stock' is too terse to serve as a scope 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?

There is no explicit guidance on when to use this versus alternatives such as tds_reserve_kit_stocktake or tds_archive_sleeve_stocktake, nor any when-not conditions or prerequisites. The phrase 'Market table stock' hints at a domain but gives no actionable selection criterion.

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.