Skip to main content
Glama

The Doll Scout Home Tools

Reconcile item counts · Objects in a photo batch

tds_photo_batch_stocktake
Read-onlyIdempotent

Compare two bounded lists on exact line IDs and show shortages, extras and repeat scans. Objects in a photo batch. Tolerated variance per photo object 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>",
      "photoIdTolerance": "<photoIdTolerance>"
    },
    "name": "tds_photo_batch_stocktake"
  }
}

Input Schema

NameRequiredDescriptionDefault
countedIdsYes
expectedIdsYes
photoIdToleranceYes

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 establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavior about exact-ID comparison, repeat scans, and tolerated variance, but does not explain how lists are encoded, how tolerance is applied, or what the result structure looks like.

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 first sentence is front-loaded and useful, but the following fragments are weak: 'Objects in a photo batch' largely repeats the title, and 'Tolerated variance per photo object ID' mostly restates a parameter name rather than adding compact guidance.

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?

For a three-required-parameter tool with no schema descriptions and no output schema, the definition is missing critical input-format details and tolerance semantics. It does state the comparison outcome categories, but an agent could still not reliably construct the expectedIds or countedIds values from this description alone.

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 parameter meaning. It conceptually maps all three parameters by mentioning two bounded lists on exact line IDs and tolerated variance per photo object ID, but it never explains list encoding, ordering, or what the tolerance integer actually controls.

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: comparing two bounded line-ID lists and reporting shortages, extras, and repeat scans. It clearly distinguishes a photo-batch reconciliation task, though it does not explicitly compare itself against any 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?

Usage is implied by the reconciliation framing and the mention of exact line IDs, shortages, extras, and tolerances. There is no explicit when-to-use guidance, no exclusions, and no named alternative for other stocktake operations.

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.