Skip to main content
Glama

The Doll Scout Home Tools

Reconcile item counts · Binder card identifiers

tds_card_binder_stocktake
Read-onlyIdempotent

Compare two bounded lists on exact line IDs and show shortages, extras and repeat scans. Binder card identifiers. Tolerated variance per card identifier.

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>",
      "binderLineTolerance": "<binderLineTolerance>"
    },
    "name": "tds_card_binder_stocktake"
  }
}

Input Schema

NameRequiredDescriptionDefault
countedIdsYes
expectedIdsYes
binderLineToleranceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/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 genuinely non-structured information: matching is on exact line IDs, and the result reports shortages, extras and repeat scans — the only disclosure of return content, since no output schema exists. It stops short of explaining what variance tolerance actually suppresses in 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 operating sentence is front-loaded and free of padding. The two following fragments are noun phrases without verbs, and 'Binder card identifiers' largely restates the title, so part of the text does not earn its place.

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 read-only, three-parameter reconciliation tool with no output schema, disclosing the output categories is a meaningful plus. The gaps that matter for correct invocation — the string encoding of the two lists and the unit/effect of the tolerance value — are left unaddressed.

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% across three required parameters, so the description carries the burden and partially meets it: 'two bounded lists on exact line IDs' maps to expectedIds/countedIds, and 'Tolerated variance per card identifier' maps to binderLineTolerance. However, it never states how the list strings are encoded (delimiter, one ID per line), that they are capped at 1600 characters, or whether tolerance is a count of units or a percentage.

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 verb and operation: compare two bounded lists on exact line IDs and report shortages, extras and repeat scans. The trailing fragment 'Binder card identifiers' scopes it to the binder-card domain and plausibly separates it from the other *_stocktake siblings, though the fragment is too terse to make that separation explicit.

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 when-to-use or when-not-to-use guidance at all. The definition never tells the agent how to choose between this and the many sibling stocktake tools (archive sleeve, borrowed items, event kit, etc.), leaving the choice to inference from the name and title alone.

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.