Skip to main content
Glama

The Doll Scout Home Tools

Reconcile item counts · Loose model accessories

tds_loose_accessory_stocktake
Read-onlyIdempotent

Compare two bounded lists on exact line IDs and show shortages, extras and repeat scans. Loose model accessories. Tolerated variance per accessory.

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>",
      "accessoryTolerance": "<accessoryTolerance>"
    },
    "name": "tds_loose_accessory_stocktake"
  }
}

Input Schema

NameRequiredDescriptionDefault
countedIdsYes
expectedIdsYes
accessoryToleranceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 behavior, so the safety profile is covered. The description adds useful behavioral detail: comparison is on exact line IDs, and results include shortages, extras, and repeat scans, plus a tolerance concept. However, it does not explain the return format, how tolerance affects the result, or what 'bounded' means in practice.

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 description is three short sentences with no wasted words, and it leads with the core comparison action before adding domain and tolerance details. The fragment 'Loose model accessories.' is slightly abrupt but serves a scoping purpose.

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, read-only comparison tool with no output schema, the description covers purpose, matching rule, result categories, and tolerance. It falls short on parameter formatting, how inputs are parsed, and whether matched-by-tolerance items appear in the result. An agent would still need to guess at call correctness details.

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 must carry the burden. It references all three parameters at a high level: 'two bounded lists' for expectedIds and countedIds, 'exact line IDs' as a format hint, and 'tolerated variance per accessory' for accessoryTolerance. It does not specify list formatting (delimiters, encoding), how the 1600-character limit is applied, or how tolerance values change the output.

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 states a specific verb and resource: 'Compare two bounded lists on exact line IDs and show shortages, extras and repeat scans.' It also scopes the domain with 'Loose model accessories.' It does not explicitly contrast with the many sibling stocktake tools, but the domain scoping separates it adequately.

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 description gives no when-to-use guidance, no prerequisites, and no alternatives or exclusions. An agent can infer this is for stocktaking loose model accessories, but there is no explicit routing to or away from sibling tools.

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.