Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Lodge Dutch Oven Knob

tds_purchase_m_lodge_dutch_oven_knob
Read-onlyIdempotent

Recorded model Dutch Oven Knob. 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_lodge_dutch_oven_knob"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/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 essentially nothing beyond them — it does not explain what happens when a model is unmatched, whether the check returns pass/fail, or what the caller learns from the call.

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?

Only two short sentences, so nothing is bloated, but the first sentence is wasted space (it repeats the title/product) and the substantive guidance about measurements is compressed into one clause. Front-loading is acceptable but the content density is low.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-required-parameter, no-output-schema tool, the definition leaves the central question — what the call produces (a fit verdict?) and what the numeric thresholds mean — unaddressed. Annotations cover read safety, but the agent still lacks enough to invoke confidently with correct measurements.

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% for five required parameters, so the description must carry the burden and largely does not. It hints that one parameter is the seller's model field and the others are measurements including "required clearances", but it never distinguishes shelfDepthCm from productDepthCm, nor useClearanceCm from frontClearanceCm, and states no units.

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 Dutch Oven Knob" largely restates the title and product name rather than stating what the tool does — presumably verifying that this specific product fits a shelf/kitchen space. There is no verb describing the operation or its outcome, so an agent cannot tell whether it records a model, looks one up, or computes a fit.

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 two sentences give input advice (use the seller's model field or exact variant name; use variant measurements including clearances) but never say when to call this tool versus the many sibling product tools or tds_quote_storage_space. No preconditions, no exclusions, no alternative routing.

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.