Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Lodge 10.25 Inch Seasoned Cast Iron Skillet

tds_purchase_c06
Read-onlyIdempotent

Recorded model L8SK3. 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_c06"
  }
}

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 cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds little beyond that — 'use measurements for the exact variant, including required clearances' hints that a fit evaluation occurs, but never says what result is produced or what constitutes a pass/fail. No output schema exists to compensate.

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 sentences, so there is no padding, but the leading 'Recorded model L8SK3' is a hard-coded fact that reads as noise rather than a front-loaded purpose statement. Brevity here is under-specification rather than efficiency.

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-parameter geometry/clearance tool with 0% schema coverage, no output schema, and no annotation detail about results needs far more: units for the four numeric fields, how the clearance values combine, and what the tool returns. Nearly everything an agent needs beyond the parameter names is missing.

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 carry the burden. It only loosely maps to offeredModel ('seller's model field or exact variant name') and vaguely gestures at the measurement params via 'measurements ... including required clearances'. The distinction between shelfDepthCm, productDepthCm, useClearanceCm, and frontClearanceCm — and their units — is left entirely unexplained.

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?

The description never states what the tool does — it opens with 'Recorded model L8SK3' and gives only input guidance. The actual purpose ('check kitchen space / fit for a skillet') must be inferred from the title, not the description text. An agent reading only the description cannot tell this is a fit/clearance check rather than a purchase or lookup tool.

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 guidance on which value to supply, not when to call this tool versus the many sibling purchase tools. No preconditions, no exclusions, no pointing to alternatives such as tds_quote_storage_space.

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.