Skip to main content
Glama

The Doll Scout Home Tools

Calculate the review date · Case seal inspection

tds_reusable_case_seal_review
Read-onlyIdempotent

Add a schedule supplied by you to a known review date and compare it with your as-of date. Case seal inspection. Your seal inspection 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>",
      "sealInspectionDays": "<sealInspectionDays>"
    },
    "name": "tds_reusable_case_seal_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfDateYes
lastReviewDateYes
sealInspectionDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/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 fully covered. Beyond that the description adds nothing: it doesn't say whether the comparison is inclusive or exclusive at the boundary, whether dates must be ISO-formatted, or what the result looks like — the substantive behavioral questions for a date computation.

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?

Short enough, with the core operation first, but two of the three sentences are noun fragments ('Case seal inspection.' / 'Your seal inspection interval in days.') that repeat the tool name and title rather than adding information. The opening clause 'Add a schedule supplied by you' is wordy for what is simply an interval in days.

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 and no parameter descriptions, the description is the only place the return value could be explained, and it isn't. For a pure-computation tool the agent cannot tell whether it will receive a boolean due flag, a computed date, or a day count — a material gap for correct downstream use.

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 carries the burden. It does map the three parameters onto the computation (review date, as-of date, and 'interval in days'), which supplies the missing unit for sealInspectionDays, but it never states the expected date string format or the meaning of the 1–730 bound.

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 does convey the operation — add an interval to a known review date and compare the result to an as-of date — but it phrases it obliquely ('Add a schedule supplied by you') and leaves the actual output (is the case seal inspection due? days remaining?) for the agent to infer. The fragment 'Case seal inspection.' restates the title rather than clarifying scope, and nothing distinguishes this from other tds_*_review siblings.

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 statement of when this tool should be used versus alternatives, no prerequisites, and no exclusions. Among the many sibling '*_review' tools (archive_snapshot_review, exhibit_condition_review, shelf_dust_review, etc.), nothing tells the agent why a case seal check uses this arithmetic tool rather than one of those.

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.