Skip to main content
Glama

The Doll Scout Home Tools

Estimate cleaning upkeep cost · eufy Saug- und Wischroboter HydroJet S2

tds_purchase_m_eufy_t2081g11
Read-onlyIdempotent

Recorded model Saug- und Wischroboter HydroJet S2. 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_eufy_t2081g11"
  }
}

Input Schema

NameRequiredDescriptionDefault
usesPerPackYes
offeredModelYes
starterPriceYes
remainingUsesYes
replacementPackPriceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior3/5

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

Annotations already declare this read-only, idempotent, non-destructive and closed-world, so safety behavior is covered. The description adds a small amount of context by pinning the price source ('amount that will appear on the order') and requiring currency consistency. It does not disclose what the estimate represents (per year? per pack cycle?), so behavioral value beyond the annotations is thin but non-zero.

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, well-formed sentences with no padding, but the leading sentence is wasted on restating the model name instead of front-loading the tool's purpose. Size is appropriate; ordering is not.

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 5-parameter, no-output-schema computation tool, the description does not say what is being computed, in what unit, or what the returned figure means, and it leaves two required integer inputs unexplained. An agent can fill the fields it understands but cannot confidently predict the result.

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 5 required parameters, so the description must carry the full burden. It gives usable meaning for offeredModel and the two price fields, but says nothing about usesPerPack or remainingUses, which are the inputs that actually drive the calculation, leaving half the parameters ambiguous.

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 'Recorded model Saug- und Wischroboter HydroJet S2', which restates the product name rather than stating what the tool does. The actual function (computing an upkeep/consumable cost from prices and usage counts) appears only in the title, never in the description body, so an agent cannot tell from the description what output to expect.

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 'Use the seller's model field or exact variant name', 'Enter prices in the same currency', and 'Use the amount that will appear on the order' are input conventions, not when-to-use guidance. Nothing distinguishes this estimator from the many sibling per-model purchase tools or states any precondition 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.