Skip to main content
Glama

The Doll Scout Home Tools

Estimate cleaning upkeep cost · Roborock F25 ALT Nass- und Trockenstaubsauger

tds_purchase_m_roborock_roborock_f25alt
Read-onlyIdempotent

Recorded model F25 ALT Nass- und Trockenstaubsauger. Use the seller’s model field or exact variant name. Enter prices in the same currency. Use the amount that will appear on the order.

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": {
      "offeredModel": "<offeredModel>",
      "starterPrice": "<starterPrice>",
      "replacementPackPrice": "<replacementPackPrice>",
      "usesPerPack": "<usesPerPack>",
      "remainingUses": "<remainingUses>"
    },
    "name": "tds_purchase_m_roborock_roborock_f25alt"
  }
}

Input Schema

NameRequiredDescriptionDefault
usesPerPackYes
offeredModelYes
starterPriceYes
remainingUsesYes
replacementPackPriceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, but the description adds nothing about behavior: no hint about what the estimate represents, whether it is per-use or per-pack, rounding, or units. The only behavioral hint is procedural ('Use the amount that will appear on the order'), which constrains inputs rather than describing the tool's conduct.

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?

Three short sentences with no filler and the model identity front-loaded, which is good. But the opening sentence merely restates the title's model label and the remaining content is terse to the point of being cryptic about the tool's actual function.

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 five-required-parameter computation tool with no output schema and no parameter descriptions, the definition should explain what comes back and how the inputs combine. It leaves the return value and two central inputs undefined, so an agent cannot reason about correctness of the estimate.

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 the load; it partially does by defining the model string, requiring both prices in one currency, and specifying which price figure to enter. It says nothing at all about 'usesPerPack' or 'remainingUses', the two parameters that drive the calculation, so a third of the schema remains unexplained.

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 never states an action verb or what the tool computes; it only pins the subject ("Recorded model F25 ALT Nass- und Trockenstaubsauger"). The verb lives in the title ("Estimate cleaning upkeep cost"), so an agent must combine title and description. It does, however, identify the exact variant, which is what separates it from the many sibling model-specific 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?

The sentences read as data-entry rules (which model string to use, currency consistency, order amount) rather than when-to-call guidance. There is no statement about when this tool applies versus the neighboring variant tools, nor any prerequisite or exclusion.

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.