Skip to main content
Glama

The Doll Scout Home Tools

Estimate remaining supplies · Protective sleeves

tds_sleeve_reserve
Read-onlyIdempotent

Use counted stock, units per task and reserved supplies to calculate throughput and shortfall. Protective sleeves. Sleeves reserved for later periods.

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>",
      "sleevesHeldBack": "<sleevesHeldBack>"
    },
    "name": "tds_sleeve_reserve"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsOnHandYes
tasksPlannedYes
unitsPerTaskYes
sleevesHeldBackYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the useful behavioral note that reserved sleeves are held for later periods and are therefore excluded from available stock, but says nothing about what the calculation returns, rounding, or units.

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?

Three short sentences, front-loaded with the calculation and its inputs, then the resource, then the reservation caveat. Slightly fragmentary ('Protective sleeves.') but nothing is wasted or buried.

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?

With no output schema, the description should explain what throughput and shortfall actually are and in what units; it names them but never defines them. For a four-required-parameter estimation tool with 0% schema coverage, one more sentence on the return values and on tasksPlanned would make it complete.

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%, so the description must carry parameter meaning and it partially does: 'counted stock' maps to unitsOnHand, 'units per task' to unitsPerTask, and 'sleeves reserved for later periods' to sleevesHeldBack. tasksPlanned is never referenced explicitly (only obliquely via 'shortfall'), and no units or bounds are given, so the compensation is incomplete.

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 description names a verb ('calculate') and outputs ('throughput and shortfall') and scopes the resource to protective sleeves, so the general purpose is inferable. But it never says what a 'throughput' or 'shortfall' value means, and it does not distinguish this estimator from the many sibling '*_reserve' tools, leaving the agent to guess which one applies.

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 explicit when-to-use statement, no when-not-to-use, and no named alternative among siblings such as tds_archive_sleeve_stocktake or tds_labels_reserve. The only guidance is an input-oriented 'use counted stock, units per task and reserved supplies', which describes mechanics rather than the situation that selects this tool.

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.