Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Hario Electric Kettle Lyra

tds_purchase_m_hario_electric_kettle_lyra
Read-onlyIdempotent

Recorded model Electric Kettle Lyra. Use the seller’s model field or exact variant name. Use measurements for the exact variant, including required clearances.

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>",
      "shelfDepthCm": "<shelfDepthCm>",
      "productDepthCm": "<productDepthCm>",
      "useClearanceCm": "<useClearanceCm>",
      "frontClearanceCm": "<frontClearanceCm>"
    },
    "name": "tds_purchase_m_hario_electric_kettle_lyra"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

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?

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. Beyond that, the description adds no behavioral context: it does not say the call evaluates fit against clearances, what a failing result implies, or whether any state is recorded despite the 'Recorded model' phrasing, which is ambiguous under a readOnlyHint.

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?

Two short sentences with no padding, so it is efficiently sized. However, the opening sentence spends its budget restating the product name instead of front-loading the actual operation, so the structure is tight but mis-ordered.

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?

With five required parameters, no output schema, and no parameter descriptions, the definition should explain what the measurements mean and what the caller gets back. It leaves the core question — is a fit verdict returned, and against which dimension — entirely unanswered.

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 numeric parameters, so the description must carry the burden. It only loosely maps to offeredModel and to the clearance/depth measurements, leaving shelfDepthCm, productDepthCm, useClearanceCm and frontClearanceCm unexplained (units, whether mm or cm, and whether clearances are per-side) — names alone are doing most of the work.

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 Electric Kettle Lyra', which restates the product name rather than stating a verb and resource. Only the title ('Check kitchen space') hints at a fit/clearance check; the body never says what the tool actually computes or returns, so an agent cannot distinguish it confidently from sibling purchase/storage 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?

'Use the seller's model field or exact variant name' and 'use measurements for the exact variant' are input-sourcing hints, not when-to-use guidance. Nothing states when this check should be invoked versus e.g. tds_quote_storage_space, nor any prerequisite such as having already obtained shelf dimensions.

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.