Skip to main content
Glama

The Doll Scout Home Tools

Reconcile item counts · Archived sleeve packs

tds_archive_sleeve_stocktake
Read-onlyIdempotent

Compare two bounded lists on exact line IDs and show shortages, extras and repeat scans. Archived sleeve packs. Tolerated variance per sleeve 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>",
      "sleevePackTolerance": "<sleevePackTolerance>"
    },
    "name": "tds_archive_sleeve_stocktake"
  }
}

Input Schema

NameRequiredDescriptionDefault
countedIdsYes
expectedIdsYes
sleevePackToleranceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent operation. Beyond that, the description usefully discloses that matching is on exact line IDs, that results include shortages, extras, and repeat scans, and that tolerance is applied per sleeve ID.

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?

The definition is compact and front-loads the comparison action, with each sentence adding scoping or parameter meaning. The telegraphic fragments are efficient, though slightly less clear than a polished sentence would be.

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-parameter reconciliation tool with no output schema and no schema descriptions, the description covers the purpose, result categories, and tolerance semantics. It still omits the list string format and does not fully explain the return structure, so an agent could invoke it incorrectly on parameter encoding.

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 description coverage, the description partially compensates by identifying the two lists as line-ID lists and explaining that sleevePackTolerance is a per-sleeve variance allowance. However, it never specifies the string encoding/delimiter for expectedIds and countedIds, leaving a material gap for required 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?

The description gives a specific verb and resource: compare two bounded line-ID lists and report shortages, extras, and repeat scans, scoped to archived sleeve packs. This clearly identifies the operation, though it does not explicitly contrast itself with the many sibling 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The archived-sleeve-pack scope and the comparison operation imply when the tool is relevant, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative.

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.