Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Lodge Diner Griddle Set

tds_purchase_m_lodge_diner_griddle_set
Read-onlyIdempotent

Recorded model Diner Griddle Set. 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_diner_griddle_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered structurally. Beyond that, the description adds only a weak instruction about matching the exact variant; it does not say what the check returns (a pass/fail fit verdict?), what happens when clearances fail, or whether results are cached/recorded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with no filler, and the model-identification requirement is front-loaded. The wording is terse to the point of being cryptic ('Recorded model'), but nothing is structurally wasteful.

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 mandatory numeric parameters at 0% schema coverage and no output schema, the description should explain each measurement and what a successful versus failing check looks like. It leaves four of five parameters' meaning to inference and says nothing about the response, which is inadequate for a compatibility-checking tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 real weight here. It partially compensates by mapping 'offeredModel' to the seller's model field or exact variant name and by signaling that the depth/clearance values must correspond to that exact variant, but it never distinguishes shelfDepthCm from productDepthCm or useClearanceCm from frontClearanceCm.

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 opens with 'Recorded model Diner Griddle Set,' which restates the resource but supplies no verb describing the operation; only the title's 'Check kitchen space' implies a fit/compatibility check. Given the tool name's 'purchase' prefix, an agent could easily mistake this for a purchase action rather than a read-only space check.

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?

'Use the seller's model field or exact variant name' is input guidance, not when-to-use guidance. There is no statement of when this tool applies versus alternatives such as a storage-space quote or the sibling cast iron griddle tool, and no prerequisites or exclusions are given.

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.