Skip to main content
Glama

The Doll Scout Home Tools

Calculate the review date · Condition photo update

tds_condition_photo_review
Read-onlyIdempotent

Add a schedule supplied by you to a known review date and compare it with your as-of date. Condition photo update. Your photo 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>",
      "conditionPhotoDays": "<conditionPhotoDays>"
    },
    "name": "tds_condition_photo_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfDateYes
lastReviewDateYes
conditionPhotoDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive calculation, so safety and mutation behavior are covered. The description adds that it performs an additive comparison between dates, but it does not explain the result shape, boundary behavior, or date-handling assumptions.

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 front-loads the operation, but the following fragments "Condition photo update" and "Your photo review interval in days" add little clarity. The overall text is short but uneven and not tightly structured.

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 three-parameter calculation with no parameter descriptions and no output schema, the description is under-specified. It omits the return value, date format expectations, and comparison semantics, leaving key behavior to inference.

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 loosely maps the three inputs as a supplied schedule, a known review date, and an as-of date, and mentions an interval in days, but it does not specify date format, inclusive/exclusive behavior, or the day-count maximum.

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 implies a date calculation: add an interval to a known review date and compare it with an as-of date. However, it never explicitly states that it calculates a review date or returns a comparison, and phrases like "schedule supplied by you" and "Condition photo update" are vague. It does not distinguish this from 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 guidance on when to use this tool versus alternatives. The description gives no context about appropriate inputs, preconditions, or the kind of review scenario it is meant to handle.

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.