Skip to main content
Glama

The Doll Scout Home Tools

Estimate cleaning upkeep cost · eufy G50 Hybrid

tds_purchase_m_eufy_t2212g11
Read-onlyIdempotent

Recorded model G50 Hybrid. 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_t2212g11"
  }
}

Input Schema

NameRequiredDescriptionDefault
usesPerPackYes
offeredModelYes
starterPriceYes
remainingUsesYes
replacementPackPriceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/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 only that the model is recorded and price-entry rules, but does not disclose what the tool calculates, how parameters interact, or what the result contains.

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 obvious filler, and the model and price instructions are front-loaded. The structure is efficient, though slightly fragmented across sentences.

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 estimation tool with no output schema and zero schema descriptions, the definition is incomplete: it never states what is being estimated, how usesPerPack or remainingUses affect the result, or what the response contains. Important context is missing for correct invocation.

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?

With 0% schema description coverage, the description must carry parameter meaning. It clarifies offeredModel ('use the seller’s model field or exact variant name') and both price fields ('same currency', 'amount that will appear on the order'), but leaves usesPerPack and remainingUses completely unexplained, so two required integer parameters remain opaque.

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 says 'Recorded model G50 Hybrid' and gives input instructions, but never states the tool's verb or purpose (e.g., 'estimate cleaning upkeep cost'). An agent must infer the calculation from the title and parameter names, and there is no differentiation from sibling purchase-model 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?

Provides guidance on which model field to use and currency consistency for prices, but gives no when-to-use criteria, prerequisites, or mention of alternative tools. It does not clarify when this estimator should be chosen over related purchase tools.

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.