Skip to main content
Glama

The Doll Scout Home Tools

Calculate the review date · Padding supply review

tds_pad_supply_review
Read-onlyIdempotent

Add a schedule supplied by you to a known review date and compare it with your as-of date. Padding supply review. Your padding 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>",
      "padSupplyDays": "<padSupplyDays>"
    },
    "name": "tds_pad_supply_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfDateYes
padSupplyDaysYes
lastReviewDateYes

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?

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world calculation. The description adds the computational behavior, but it does not disclose expected date formats, boundary behavior for padding intervals, or how the comparison result is represented.

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 description is short and front-loads the calculation. The fragment 'Padding supply review.' largely restates the name/title and does not add much, but overall 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?

There is no output schema, so the description should explain what the calculation returns. It says to compare dates but does not state whether the result is a date, a boolean, a status, or a fuller comparison object, leaving a significant gap for invocation and interpretation.

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?

With 0% schema description coverage, the description must carry parameter meaning. It maps all three parameters conceptually: known review date, as-of date, and padding review interval in days. However, it does not specify the date string format or clarify the exact returned comparison despite the 10-character date constraints.

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 computation: add the supplied padding interval to a known review date and compare against an as-of date. This is enough to distinguish it as a date-calculation tool, though 'padding supply review' is jargon and it does not explicitly differentiate itself from 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 explicit guidance on when to use this tool versus alternatives, nor any when-not conditions or prerequisites. The only implied context is that the caller has a known last review date and an as-of date.

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.