Skip to main content
Glama

The Doll Scout Home Tools

Compare two all-in quotes · Display cabinet rental options

tds_quote_cabinet_lease
Read-onlyIdempotent

Add each recurring cost over your chosen comparison period to the one-time quote. Display cabinet rental options. Rental period in months.

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>",
      "cabinetLeaseMonths": "<cabinetLeaseMonths>"
    },
    "name": "tds_quote_cabinet_lease"
  }
}

Input Schema

NameRequiredDescriptionDefault
cabinetLeaseMonthsYes
offerAMonthlyCentsYes
offerAUpfrontCentsYes
offerBMonthlyCentsYes
offerBUpfrontCentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and closed-world, so the safety profile is fully covered by structured data. The description does add one genuine behavioral fact beyond that: the computation is upfront plus monthly multiplied across the chosen period. It does not say what the result looks like, whether both offers are returned, or whether a winner/delta is indicated.

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, and the core formula is front-loaded, which is good. However, 'Display cabinet rental options' duplicates the title and carries no operational meaning, and 'Rental period in months' is a fragment restating a schema constraint — two of three sentences do little work.

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, five undocumented parameters, and no annotations gap to lean on, the description should explain what is returned (e.g., per-offer totals and which is cheaper). It does not, leaving the agent unable to predict the result shape of a pure computation tool.

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 carries the full burden and only partially meets it. 'One-time quote' loosely maps to the two upfront-cent parameters and 'recurring cost' to the two monthly parameters, and 'Rental period in months' clarifies cabinetLeaseMonths' unit. It never explains the cents unit, the maximum of 120 months, or the A/B pairing convention.

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 first sentence conveys the core operation: folding recurring costs over a comparison period into a one-time quote, which implies a total-cost comparison between two offers. But the verb+resource are never named explicitly (no mention of offer A vs offer B, no mention of returning a comparison), and the trailing fragments 'Display cabinet rental options. Rental period in months.' restate the title and a parameter rather than sharpening the purpose. An agent can guess it computes totals, but not exactly what it produces.

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 when-to-use guidance, no conditions or prerequisites, and no reference to any alternative tool for quoting or comparing costs. The sibling set contains many other tds_quote_* tools, and nothing here helps an agent choose between them.

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.