Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · ThermoWorks Thermapen® IR

tds_purchase_m_thermoworks_thermapen_ir
Read-onlyIdempotent

Recorded model Thermapen® IR. 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_thermapen_ir"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/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 fully covered structurally. The description adds a useful behavioral hint — measurements must reflect the exact variant and include required clearances — implying a fit-validation step, but it never says what happens when a dimension fails, nor what the call produces.

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 filler, but the opening "Recorded model Thermapen® IR." simply restates the title in opaque phrasing and earns little. The actionable content (model field, measurements, clearances) is present but not front-loaded as a purpose statement.

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, undocumented parameters and no output schema, the definition leaves the agent guessing at units, how shelf/product depth and the two clearances interact, and what a successful or failing result looks like. For a dimension-validation tool this is a substantial omission.

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 parameters, so the description carries the burden and only partly meets it. It clarifies that offeredModel should come from the seller's model field and that measurements must match the exact variant including clearances, but it never distinguishes shelfDepthCm from productDepthCm, nor useClearanceCm from frontClearanceCm, and gives no unit or tolerance semantics.

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 description pins the tool to one specific SKU ("Thermapen® IR") and gestures at a fit/measurement check via "measurements... including required clearances," but it never states a verb or outcome — no "check whether it fits," "validate," or "record." An agent can tell which product it belongs to but not precisely what operation is performed.

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 parameter sourcing ("Use the seller's model field or exact variant name"), not when to use this tool versus alternatives. Nothing routes the agent away from the many sibling model tools such as thermapen_nano, thermapen_one, dash, or dot, nor is any prerequisite or failure condition described.

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.