Skip to main content
Glama

The Doll Scout Home Tools

Compare two all-in quotes · Shelf care costs

tds_quote_shelf_care
Read-onlyIdempotent

Add each recurring cost over your chosen comparison period to the one-time quote. Shelf care costs. Months of estimated shelf care.

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": {
      "offerAUpfrontCents": "<offerAUpfrontCents>",
      "offerBUpfrontCents": "<offerBUpfrontCents>",
      "offerAMonthlyCents": "<offerAMonthlyCents>",
      "offerBMonthlyCents": "<offerBMonthlyCents>",
      "shelfCareMonths": "<shelfCareMonths>"
    },
    "name": "tds_quote_shelf_care"
  }
}

Input Schema

NameRequiredDescriptionDefault
shelfCareMonthsYes
offerAMonthlyCentsYes
offerAUpfrontCentsYes
offerBMonthlyCentsYes
offerBUpfrontCentsYes

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description adds almost nothing beyond that: it does not say what is returned (per-offer totals? a delta?), whether values are in cents, or how the amortization over shelfCareMonths is computed. For a pure calculator whose entire value is the formula, this is a meaningful gap.

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?

It is short, but the brevity comes from under-specification rather than tight writing. The two trailing sentence fragments ("Shelf care costs. Months of estimated shelf care.") are near-duplicative and add no information, and the useful instruction is not front-loaded with any result statement.

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 five required numeric inputs, no output schema, and a computation whose formula is entirely implicit, the description should explain what total is produced and how months factor in. It leaves the agent guessing whether the return is two totals, a difference, or a per-month figure, which is not sufficient for correct invocation.

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 five required parameters, so the description must carry the semantic load and does not. It alludes to one-time vs recurring costs and a comparison period, but never disambiguates offerA vs offerB fields, never states that amounts are in cents, and never explains that shelfCareMonths is the amortization horizon bounded at 1–120.

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 states an arithmetic intent ("Add each recurring cost over your chosen comparison period to the one-time quote"), which implies a total-cost comparison of two offers, but it never names the tool's actual output or explicitly frames it as an A-vs-B comparison. The trailing fragments "Shelf care costs. Months of estimated shelf care." restate the topic rather than sharpen 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 guidance on when to use this versus the many sibling quote tools (e.g. tds_quote_cabinet_lease, tds_quote_storage_space) or versus a simple break-even calculation. No prerequisites, no statement of what inputs must represent, and no when-not-to-use condition.

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.