Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Lodge Cast Iron Griddle

tds_purchase_m_lodge_cast_iron_griddle
Read-onlyIdempotent

Recorded model Cast Iron Griddle. 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_iron_griddle"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly=true, idempotent=true, destructive=false and closed-world, so the safety profile is covered externally. Beyond that the description adds no behavior: it doesn't say what is computed from the clearances or what a caller receives back, which matters because there is no output schema.

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?

It is short and the actionable sentences come early, so there is no bloat. However, the opening sentence is a pure tautology that consumes roughly a third of the text without adding information.

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-required-parameter evaluation tool with no output schema and no parameter documentation, the description is thin: it explains neither the fit logic, the units, nor the result. An agent would have to guess at both input meaning and expected output.

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 must compensate, and it only loosely gestures at them ("model field or exact variant name", "measurements ... including required clearances"). It never distinguishes shelfDepthCm from productDepthCm, nor explains how useClearanceCm and frontClearanceCm are interpreted or which units apply.

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 Griddle" restates the tool name and title rather than stating what the tool does. Only the title ("Check kitchen space") hints that this evaluates whether the griddle fits, and the description never names the action or the outcome.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives input-side guidance (use the seller's model field or exact variant name, use measurements for the exact variant), which is an implied usage hint. It says nothing about when to prefer this over sibling product tools 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.