Skip to main content
Glama

The Doll Scout Home Tools

Estimate remaining supplies · Protective poly bags

tds_sealed_bags_reserve
Read-onlyIdempotent

Use counted stock, units per task and reserved supplies to calculate throughput and shortfall. Protective poly bags. Bags reserved for re-packing.

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": {
      "unitsOnHand": "<unitsOnHand>",
      "unitsPerTask": "<unitsPerTask>",
      "tasksPlanned": "<tasksPlanned>",
      "bagsHeldBack": "<bagsHeldBack>"
    },
    "name": "tds_sealed_bags_reserve"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsOnHandYes
bagsHeldBackYes
tasksPlannedYes
unitsPerTaskYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds nothing further — it does not say whether the result is a count, a pass/fail, or how shortfall is derived, nor does it mention rounding or whether bagsHeldBack is subtracted before or after the throughput division.

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 earns its place, but the following two fragments ('Protective poly bags. Bags reserved for re-packing.') are label-like and partly redundant with each other, reading as catalog metadata rather than usable instruction.

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?

With four required numeric parameters, zero schema descriptions, and no output schema, the description needed to explain the calculation and the shape of the result. It does neither, leaving the agent unable to predict what 'throughput' and 'shortfall' mean or how the inputs combine.

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 the burden for all four required parameters. It loosely maps 'counted stock', 'units per task', and 'reserved supplies' onto unitsOnHand, unitsPerTask, and bagsHeldBack, but never addresses tasksPlanned and gives no units, ordering, or edge-case semantics for any of them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb phrase 'calculate throughput and shortfall' is specific, but the resource is only obliquely identified through the fragments 'Protective poly bags' and 'Bags reserved for re-packing.' An agent can guess this is a supply-estimation tool for poly bags, but the connection between the calculation and the bag domain is implied rather than stated.

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 guidance, no preconditions, and no pointer to an alternative such as a stocktake or reserve sibling. The description never says whether this is for planning a run, auditing stock, or reordering, so an agent has no routing signal beyond the name.

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.