Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · ThermoWorks DOT® Simple Alarm Thermometer

tds_purchase_m_thermoworks_dot
Read-onlyIdempotent

Recorded model DOT® Simple Alarm Thermometer. 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_thermoworks_dot"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/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 the constraint that measurements must correspond to the exact variant and include required clearances, which is useful usage context, but it never states what the tool produces (a fit verdict? stored record?) despite having no output schema.

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 sentences with no padding, though the leading sentence is largely a restatement of the product name and the genuinely informative measurement guidance arrives last rather than front-loaded.

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-required-parameter check tool with no output schema and no parameter documentation, the description should explain what the numbers mean and what result comes back. Neither is present, so an agent cannot confidently construct a correct call from the definition alone.

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 coverage is 0%, so the description must carry the parameter burden. It clarifies offeredModel (seller's model field or exact variant name) and gestures at the two clearance parameters via "required clearances," but leaves shelfDepthCm, productDepthCm, and useClearanceCm undefined, with no explanation of units or how the five numbers combine.

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

Purpose3/5

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

The title says "Check kitchen space" and the description hints at clearance/fit checking via "Use measurements for the exact variant, including required clearances," but the opening sentence ("Recorded model DOT® Simple Alarm Thermometer") merely restates the product name. The agent is left to infer that the tool evaluates whether this thermometer fits a shelf rather than, say, recording a purchase or quoting a price.

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 only guidance is about which value to pass ("Use the seller's model field or exact variant name"), which is parameter-level, not tool-level. Nothing says when this tool is appropriate versus a sibling such as tds_quote_storage_space or the other ThermoWorks product tools, and no prerequisites or exclusions are given.

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.