Skip to main content
Glama

The Doll Scout Home Tools

Calculate the review date · Loan file review

tds_loan_file_review
Read-onlyIdempotent

Add a schedule supplied by you to a known review date and compare it with your as-of date. Loan file review. Your loan file 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>",
      "loanFileDays": "<loanFileDays>"
    },
    "name": "tds_loan_file_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfDateYes
loanFileDaysYes
lastReviewDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/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 safety is fully covered by structured data. Beyond that, the description adds almost nothing behavioral: it does not say whether the comparison yields a boolean, a due date, or a status, and provides no output shape despite having no output schema.

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 definition is short and front-loads the computation, but the middle fragment 'Loan file review' is pure filler and the closing sentence restates the interval already implied by the first sentence. Redundancy rather than length is the issue.

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 zero parameter documentation, the description is the only place an agent can learn what the calculation returns and what date format to supply. It supplies neither, leaving a simple three-parameter computation tool under-explained for its actual use.

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% across three required parameters, so the description must carry the load. It hints that one input is an interval in days and another is an as-of date, but it never states the expected date format (10-character strings), the 1-730 day bound on loanFileDays, or which parameter is the base review date, leaving gaps the schema does not fill.

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 conveys the operation as adding an interval to a base review date and comparing against an as-of date, which is more specific than the title alone. However, the phrasing 'Add a schedule supplied by you' is vague and the fragment 'Loan file review' merely restates the tool name. It never states the concrete outcome (e.g., whether the file is due for review), so an agent must infer the purpose.

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 indication of when this tool should be chosen over any sibling, no prerequisites, and no statement of what it does not cover. The only contextual hint is the phrase 'Loan file review', which names a domain but gives no selection guidance.

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.