Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · ThermoWorks Thermapen® NANO

tds_purchase_m_thermoworks_thermapen_nano
Read-onlyIdempotent

Recorded model Thermapen® NANO. 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_nano"
  }
}

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 establish readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds nothing beyond that: it does not say what is computed, what happens when the clearance math fails, or what the caller receives, leaving the outcome of the call entirely opaque.

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, and the model/variant instruction is reasonably front-loaded. However, brevity here reflects under-specification rather than discipline, so the structure works but the content is too thin to earn a high score.

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-parameter, 0%-coverage schema with no output schema, the description does far too little. It never states the fit/clearance rule being evaluated or the shape of the pass/fail result, which is exactly the information an agent needs and cannot obtain from structured fields.

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 full meaning. It clarifies only that offeredModel should hold the seller's model or exact variant name, and gestures vaguely at "required clearances" without distinguishing useClearanceCm from frontClearanceCm or explaining how shelf and product depth combine with clearances.

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 Thermapen® NANO" restates the product in the tool name rather than stating what the tool does. The title says "Check kitchen space," but the description never carries a verb such as check, evaluate, or compare, so an agent must infer the action from the title alone and cannot distinguish this tool's purpose from its many sibling purchase/space 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?

The only directive is "Use the seller's model field or exact variant name," which is parameter advice, not when-to-use guidance. Nothing states when this tool should be chosen (for example, versus a generic storage-space quote, or when the variant is not NANO) or when it should not be used.

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.