Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · ThermoWorks Executive Series® Thermometer

tds_purchase_m_thermoworks_executive_series_thermometer
Read-onlyIdempotent

Recorded model Executive Series® 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_executive_series_thermometer"
  }
}

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only a note to match the exact variant and include clearances, and says nothing about what the evaluation does — whether it compares depths, flags insufficient clearance, or what happens when the variant does not match. For an evaluation-style tool with a closed-world dataset, the absence of any outcome semantics is a real gap.

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?

The text is short, but the leading sentence "Recorded model Executive Series® Thermometer." is a fragment that conveys no actionable information and pushes the only useful instruction to the middle. Remaining sentences are compact with no filler, so length itself is not the problem — front-loading is.

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 numeric parameters, no schema descriptions, no output schema and no explanation of how the measurements combine, the definition leaves the agent unable to predict the result or to know what a valid call looks like beyond passing five numbers. The description should at minimum state the fit-check logic and what a returned verdict represents. Given the tool's complexity relative to its one-line treatment, it is materially incomplete.

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 the description must carry all meaning. It clarifies offeredModel (seller's model field or exact variant name) but leaves shelfDepthCm, productDepthCm, useClearanceCm and frontClearanceCm entirely unexplained — an agent must guess which depth is the furniture and which is the appliance, and what the two clearance measures represent. With all five parameters required and undocumented, the partial coverage is inadequate.

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?

"Recorded model Executive Series® Thermometer" is a noun fragment that names the product rather than stating what the tool does; there is no verb describing the operation (fit check, clearance validation, or recording). Only the title's "Check kitchen space" hints at the function, and the title is not part of the description body. An agent cannot confidently distinguish this from siblings such as tds_quote_storage_space or the other thermoworks product tools based on 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?

"Use the seller's model field or exact variant name" is value-sourcing guidance, not when-to-use guidance; it never says when this tool should be selected over the storage-space or other product-matching siblings. "Use measurements for the exact variant, including required clearances" is similarly a data-entry instruction rather than a routing rule. No preconditions, exclusions, or alternatives are stated.

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.