Skip to main content
Glama

The Doll Scout Home Tools

Reconcile item counts · Exhibit reserve kit

tds_reserve_kit_stocktake
Read-onlyIdempotent

Compare two bounded lists on exact line IDs and show shortages, extras and repeat scans. Exhibit reserve kit. Tolerated variance per reserve 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>",
      "reservePartTolerance": "<reservePartTolerance>"
    },
    "name": "tds_reserve_kit_stocktake"
  }
}

Input Schema

NameRequiredDescriptionDefault
countedIdsYes
expectedIdsYes
reservePartToleranceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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 a closed-world scope, so the safety profile is covered. The description adds genuinely useful behavior beyond that: matching is on exact line IDs and the report distinguishes shortages, extras and repeat scans. It still omits edge behavior such as how duplicates/whitespace in the lists are handled and what happens when the two lists have no overlapping IDs.

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 operation and its outputs are front-loaded in one efficient sentence. However, the middle fragment 'Exhibit reserve kit' duplicates the title without adding meaning and breaks the flow; removing it would improve the definition without losing information.

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, the description does reasonably well by naming what the result contains (shortages, extras, repeat scans). For a read-only tool with required inputs, though, an agent still lacks the list encoding and the exact tolerance semantics needed to call it confidently, so it is adequate but incomplete.

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?

Schema description coverage is 0%, so the description must carry the burden; it partially does by signaling that expectedIds and countedIds are ID lists matched exactly and that reservePartTolerance is a per-reserve-ID variance threshold. It does not explain the encoding of the two string lists (delimiter, format) or what 'bounded' means relative to the 1600-char cap, leaving real ambiguity for a 3-required-parameter tool.

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 first sentence gives a concrete operation: compare two bounded lists on exact line IDs and report shortages, extras and repeat scans. That is enough to tell it is a reconciliation/stocktake-diff tool. It does not differentiate itself from the many sibling stocktake tools, and the fragment 'Exhibit reserve kit' restates the title rather than clarifying the resource.

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 statement of when to use this versus alternatives, no prerequisites, and no exclusions — notable given a sibling set full of other *_stocktake tools. At best, 'Tolerated variance per reserve ID' implies a threshold exists, but nothing tells the agent when this reconciliation is the right choice.

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.