Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Lodge Pan Scrapers

tds_purchase_m_lodge_pan_scrapers
Read-onlyIdempotent

Recorded model Pan Scrapers. 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_pan_scrapers"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare this is a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is clear. The description adds that inputs should identify an exact variant and include required clearances, but it does not disclose what the check returns, what happens when the variant does not fit, or any other behavioral result beyond the input constraints.

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?

The description is very short and wastes little space, but the opening phrase “Recorded model Pan Scrapers” is awkward and does not front-load the actual operation. The remaining sentences are efficient instructions, so structural clarity is decent but not perfect.

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 tool with five required, entirely undocumented parameters and no output schema, the description is too thin. It does not explain what “check kitchen space” produces or how the four measurement/clearance values interact, leaving an agent with insufficient context to invoke the tool confidently beyond copying the variant name.

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 the burden of explaining all five required parameters. It adds meaning for offeredModel by pointing to the seller’s model field or exact variant name, and it generically says to use measurements including clearances, but it does not distinguish shelfDepthCm, productDepthCm, useClearanceCm, or frontClearanceCm from one another.

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 does not clearly state the action the tool performs; “Recorded model Pan Scrapers” is not a verb-resource purpose statement. The title “Check kitchen space” and the talk of measurements and clearances imply a fit/space check, but the description itself leaves the core operation implicit rather than explicit.

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?

It gives task-level guidance to use the seller’s model field or exact variant name and to use measurements for the exact variant, including clearances. However, it provides no when-to-use guidance versus sibling tools such as the grill pan scrapers, deluxe scraper, or general storage-space quote tool, despite those being obvious alternatives.

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.