Skip to main content
Glama

The Doll Scout Home Tools

Calculate the review date · Offline archive snapshot

tds_archive_snapshot_review
Read-onlyIdempotent

Add a schedule supplied by you to a known review date and compare it with your as-of date. Offline archive snapshot. Your backup review 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>",
      "backupReviewDays": "<backupReviewDays>"
    },
    "name": "tds_archive_snapshot_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfDateYes
lastReviewDateYes
backupReviewDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already state readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the operation is offline and uses a caller-supplied schedule, but it does not disclose the result semantics, date handling, or what happens at boundary values. This is adequate additional context but not rich behavioral detail.

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?

The definition is short and front-loads the main calculation before adding context and parameter meaning. The fragments 'Offline archive snapshot.' and 'Your backup review interval in days.' are terse but serve a purpose. The phrasing 'Add a schedule supplied by you to a known review date' is slightly awkward, but there is little wasted text.

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?

For a simple three-parameter calculation, the description should explain the return or comparison outcome, especially because no output schema exists. It also omits the date format expected by the two 10-character date fields. An agent can identify the inputs, but cannot confidently predict or interpret the result.

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. It maps the three inputs in prose: a known review date, an as-of date, and a backup review interval in days. However, it does not specify the date string format or clarify how the interval is applied, leaving some ambiguity despite covering all three parameters.

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

Purpose4/5

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

The description states a specific operation: add a caller-supplied interval to a known review date and compare it with an as-of date. It also labels the context as an offline archive snapshot, though it never plainly says it calculates a due/overdue review result. It is clear enough to distinguish a date calculation from sibling review tools, but the wording is indirect.

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 gives no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternatives. 'Offline archive snapshot' and 'backup review interval' imply an archive backup review context, but the agent must infer the usage scenario from those fragments.

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.