Skip to main content
Glama

The Doll Scout Home Tools

Estimate cleaning upkeep cost · Dreame Fensterputzroboter C1

tds_purchase_m_dreame_dreame_fensterputzroboter_c1
Read-onlyIdempotent

Recorded model Fensterputzroboter C1. 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_dreame_dreame_fensterputzroboter_c1"
  }
}

Input Schema

NameRequiredDescriptionDefault
usesPerPackYes
offeredModelYes
starterPriceYes
remainingUsesYes
replacementPackPriceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. Beyond that the description only constrains input formatting; it never says that a cost estimate is produced, whether anything is stored ('Recorded model' hints at persistence but is unexplained), or what the response contains (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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences with no filler, and the model-identity constraint is front-loaded. The first sentence is largely redundant with the name/title, so it does not fully earn its place, but the remainder is tight.

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 computational tool with 0% schema coverage and no output schema, the description is thin: it does not explain the calculation (how remainingUses and usesPerPack drive the result), does not define the integer parameters, and does not indicate the return value or units 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 carries the full burden. It clarifies offeredModel (seller's model field or exact variant name) and the two price fields (same currency, amount as on the order), but leaves usesPerPack and remainingUses completely unglossed — the two integers that most need units and relationship explained for an upkeep estimate.

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 a verb+resource of its own; 'Recorded model Fensterputzroboter C1' essentially restates the tool name. The upkeep-cost intent is only recoverable from the title and inferred from the price/usage parameters, so an agent cannot confirm from the description alone what is actually computed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives data-entry guidance ('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') rather than when-to-use guidance. There is no statement of when this tool is appropriate versus a sibling model tool, nor any exclusion or precondition.

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.