Skip to main content
Glama

The Doll Scout Home Tools

Calculate the review date · Shelf dust inspection

tds_shelf_dust_review
Read-onlyIdempotent

Add a schedule supplied by you to a known review date and compare it with your as-of date. Shelf dust inspection. Your dust check interval in days.

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": {
      "lastReviewDate": "<lastReviewDate>",
      "asOfDate": "<asOfDate>",
      "dustReviewDays": "<dustReviewDays>"
    },
    "name": "tds_shelf_dust_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfDateYes
dustReviewDaysYes
lastReviewDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds that this is a pure add-and-compare computation, but says nothing about the result shape (a date? a boolean due/not-due?) or how boundary dates are handled.

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?

It is short, but the second sentence ('Shelf dust inspection.') is filler that repeats the title, and the third is a fragment referring to one parameter. The core computation is front-loaded, so it is not wasteful in length, just poorly organized.

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 no output schema, the description is the only place an agent could learn what is returned, and it does not say — leaving a calculator tool whose entire value is its result undefined. The input format and comparison semantics are also unstated at 0% schema coverage.

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 parameter meaning, yet it only glosses one input ('your dust check interval in days' for dustReviewDays) and never clarifies the difference between lastReviewDate and asOfDate or that both are 10-character date strings.

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 the operation ('Add a schedule ... to a known review date and compare it with your as-of date'), which is more than a restatement of the name, but it never states the actual purpose in domain terms (determining whether a shelf dust review is due) and never distinguishes it from the many sibling *_review tools.

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 prerequisites, and no reference to any alternative tool. An agent must infer from the name alone that this is the date-arithmetic helper rather than one of the sibling shelf/review tools.

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.