Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · ThermoWorks DASH™ Thermometer

tds_purchase_m_thermoworks_dash
Read-onlyIdempotent

Recorded model DASH™ 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_dash"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

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 readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only that the variant must match exactly and that clearances must be included — a correctness constraint, not behavior. It never states what the tool produces (a fit verdict, a quote, an error on misfit) or how a non-fitting result is surfaced.

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 sentences with no padding, but the first sentence adds almost no information beyond the title and product name, wasting the front-loaded position. The useful parameter hints are relegated to sentences two and three, so structure is adequate but not optimized.

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 tool with five required numeric/string parameters, zero schema descriptions and no output schema, the description is well short of what an agent needs. Units, the relationship between the two depth fields, the meaning of the two clearance fields, and the shape of the result (fit check outcome) are all missing, leaving the agent to guess before a mandatory-parameter call.

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%, so all five parameters carry no documented meaning; the description must compensate and only partially does. It maps offeredModel to "the seller's model field or exact variant name" and gestures at the measurement parameters via "measurements ... including required clearances," but never explains the shelfDepthCm vs productDepthCm distinction, what useClearanceCm and frontClearanceCm represent, or the units expected.

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 the fragment "Recorded model DASH™ Thermometer," which essentially restates the product name in the title rather than stating a verb and outcome. Nothing in the text says the tool evaluates whether the DASH fits on a shelf given depth and clearances, so the agent must infer the action (a space/fit check) from the parameter names alone.

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-formatting instructions, not when-to-use guidance. There is no statement of when this tool applies versus the numerous sibling product tools or a generic quote_storage_space call, and no exclusions or prerequisites 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.