Skip to main content
Glama

The Doll Scout Home Tools

Estimate remaining supplies · Reusable cloth wraps

tds_cloth_wraps_reserve
Read-onlyIdempotent

Use counted stock, units per task and reserved supplies to calculate throughput and shortfall. Reusable cloth wraps. Reusable wraps held back.

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>",
      "wrapsHeldBack": "<wrapsHeldBack>"
    },
    "name": "tds_cloth_wraps_reserve"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsOnHandYes
tasksPlannedYes
unitsPerTaskYes
wrapsHeldBackYes

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 read-only, idempotent, non-destructive, and closed-world behavior, so the description need not restate safety traits. It adds only that the tool calculates throughput and shortfall, but does not explain what is returned, how shortfall is represented, or whether the calculation includes tasksPlanned in the result. With no output schema, this leaves a meaningful behavioral gap.

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 two following fragments are redundant restatements of the tool's subject and the wrapsHeldBack parameter. The description is short, but not every sentence earns its place.

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?

This is a pure calculation tool with no output schema, so the description should explain the return values or formula. It mentions throughput and shortfall but does not describe their form or how tasksPlanned participates, leaving an agent without enough information to interpret results confidently.

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 compensate for four parameters. It alludes to counted stock, units per task, and reserved supplies, but never mentions tasksPlanned explicitly, maps these concepts to parameter names, or defines the arithmetic relationship. The parameter meaning remains ambiguous.

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 first sentence states a calculation using counted stock, units per task, and reserved supplies to produce throughput and shortfall, which is a specific verb and output concept. However, the trailing fragments 'Reusable cloth wraps. Reusable wraps held back.' add subject matter but do not clarify how this differs from other reserve or stocktake tools in the sibling list.

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 says to use counted stock and reserved supplies but gives no explicit when-to-use condition, prerequisites, or alternatives. An agent cannot tell from this text when to choose this reserve calculation over sibling tools such as stocktake or reserve-kit 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.