Skip to main content
Glama

The Doll Scout Home Tools

Estimate cleaning upkeep cost · eufy Mähroboter C15 Solo (Ohne Garage)

tds_purchase_m_eufy_t280b3a2
Read-onlyIdempotent

Recorded model Mähroboter C15 Solo (Ohne Garage). 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_t280b3a2"
  }
}

Input Schema

NameRequiredDescriptionDefault
usesPerPackYes
offeredModelYes
starterPriceYes
remainingUsesYes
replacementPackPriceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/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 openWorldHint=false, so the safety profile is covered. The description adds useful constraints (use the amount that will appear on the order, keep prices in one currency), but never states that the operation is a pure calculation with no persistence or what the computation represents.

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?

Three short, front-loaded sentences with no padding; each carries a distinct instruction. The weakness is under-specification of purpose rather than verbosity, so structure is fine but the opening sentence spends its space on model identity.

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-parameter, all-required estimation tool with no output schema and no described computation, the definition leaves the agent without enough to predict what the call produces or how the use counts feed the estimate. Two of the five parameters receive no semantic explanation anywhere.

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% with five required parameters, so the description must carry the load. It clarifies offeredModel (seller's model field or exact variant name) and partially clarifies the two price fields, but says nothing about usesPerPack or remainingUses, and does not explain how starterPrice differs from replacementPackPrice.

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 Mähroboter C15 Solo (Ohne Garage)', which restates the title's product identity rather than stating what the tool does. No verb says it estimates a cleaning upkeep/cost figure, so the only purpose signal comes from the title, not the description.

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 input conventions ('Use the seller's model field or exact variant name', 'Enter prices in the same currency') but never says when this tool should be chosen, nor points to any alternative/sibling for other models or scenarios. The guidance is about data entry, not tool selection.

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.