Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Lodge Cast Iron Mini Wok

tds_purchase_m_lodge_cast_mini_iron_wok
Read-onlyIdempotent

Recorded model Cast Iron Mini Wok. 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_cast_mini_iron_wok"
  }
}

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, idempotentHint=true and destructiveHint=false, so the safety profile is settled without the description. The description adds the constraint that measurements must correspond to the exact variant, but says nothing about what the call produces (a fit verdict? echoed dimensions?) or any limits.

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, front-loaded, with no filler — but the brevity comes at the cost of substance rather than from efficiency. The opening sentence spends its space re-identifying the product rather than saying what happens.

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?

A five-required-parameter tool with zero schema description coverage and no output schema needs the description to explain the clearance model and the expected result. Neither is present, leaving the agent unable to tell how the dimensions are evaluated or what comes back.

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 parameter meaning, and it largely does not. It gestures at the model parameter and at "measurements ... including required clearances," but never distinguishes useClearanceCm from frontClearanceCm or shelfDepthCm from productDepthCm, and units are only inferable from parameter names.

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 Cast Iron Mini Wok" restates the product name from the title rather than stating a verb and outcome. Nothing in the text says the tool checks whether the wok fits the kitchen shelf given depth and clearance measurements; the agent must infer that from the parameter names.

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 a data-entry rule ("Use the seller's model field or exact variant name"), which is not when-to-use guidance. There is no statement of when this tool is appropriate versus a generic space/storage-quote sibling, and no prerequisites or exclusions.

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.