Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Lodge Deluxe Pan Scraper

tds_purchase_m_lodge_deluxe_pan_scraper
Read-onlyIdempotent

Recorded model Deluxe Pan Scraper. 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_deluxe_pan_scraper"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so safety is largely covered. The description adds the meaningful constraint that measurements must correspond to the exact variant, including clearances, but says nothing about what the call produces or how a fit failure is represented.

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?

Two short, front-loaded sentences with little padding. The only waste is the leading nominal fragment repeating the product name, which occupies the prime opening position without conveying an action.

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 mandatory numeric parameters, zero schema coverage and no output schema, the description is too thin: it does not explain what each measurement means in physical terms or what a successful result looks like (a fit verdict, required clearance margins, etc.). An agent can supply values but cannot reason about their correctness or interpret the outcome.

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% and all five parameters are required, so the description carries the full documentation burden. It covers offeredModel reasonably ("seller's model field or exact variant name") and lumps the rest under "measurements... including required clearances," without distinguishing 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.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence, "Recorded model Deluxe Pan Scraper," merely restates the product name in the title rather than stating a verb and outcome. The remainder is input instructions ("Use the seller's model field... Use measurements..."), so the actual operation — a kitchen-space/fit check — must be inferred from the title rather than the description.

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 practical direction on which identifier to supply (seller's model field or exact variant name) and that measurements including clearances are needed. However, it never states when to use this tool versus the storage-space quote sibling, nor any exclusion such as variant unavailability, leaving the when-to-use decision implied.

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.