Skip to main content
Glama

The Doll Scout Home Tools

Estimate cleaning upkeep cost · Roborock H60 2-in-1 Akku-Staubsauger mit Power-Detect

tds_purchase_m_roborock_roborock_h60
Read-onlyIdempotent

Recorded model H60 2-in-1 Akku-Staubsauger mit Power-Detect. 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_h60"
  }
}

Input Schema

NameRequiredDescriptionDefault
usesPerPackYes
offeredModelYes
starterPriceYes
remainingUsesYes
replacementPackPriceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/5

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

The annotations already declare readOnly=true, idempotent=true, destructive=false, and openWorld=false, so the safety profile is covered. The description adds no behavioral context beyond parameter advice: it does not explain the calculation, whether inputs are persisted, or what the tool returns.

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 description is short and mostly free of filler, but the opening sentence is not front-loaded with purpose and the instructions are fragmented. Every sentence is relevant, yet the overall structure remains under-specified.

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?

The tool has five required parameters, no schema descriptions, and no output schema. The description does not explain the calculation, the two usage-count inputs, or the return value, so it is incomplete 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. The description clarifies offeredModel and gives currency/source guidance for the price fields, but it does not explain usesPerPack or remainingUses or how those inputs drive the estimate. This adds partial meaning but leaves key parameters undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a product label ("Recorded model H60...") rather than a specific verb and resource. It never states that the tool estimates cleaning upkeep cost; that purpose appears only in the title. It identifies the product but does not distinguish its purpose from sibling product variants.

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?

It gives parameter-entry instructions such as using the seller’s model field, entering prices in the same currency, and using the order amount. It provides no when-to-use or when-to-prefer guidance over alternatives, and the agent cannot tell from the description whether this is an estimate, a purchase, or a listing helper.

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.