Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Lodge Grill Pan Scrapers

tds_purchase_m_lodge_grill_pan_scrapers
Read-onlyIdempotent

Recorded model Grill 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_grill_pan_scrapers"
  }
}

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 openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the useful constraint that the model and measurements must correspond to the exact variant rather than a substitute, but says nothing about what the call returns, whether it yields a pass/fail verdict, or how clearance shortfalls are reported.

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?

Three short sentences with no filler, but the opening sentence is a truncated fragment and the guidance is front-loaded around the model field rather than around the action. Compact, yet thin rather than efficient.

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?

This is a five-required-parameter check with no output schema and no annotation-level detail about results. Given that complexity, the description should say what is measured, against what, and what outcome the agent receives; it does none of these, leaving the agent unable to predict the response.

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 semantics. It mentions 'measurements... including required clearances,' which only loosely maps onto useClearanceCm versus frontClearanceCm, and it never clarifies units (cm is implied only by parameter names), how clearances are measured, or what the maxLength 400 on offeredModel means in practice.

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 never states an action verb: 'Recorded model Grill Pan Scrapers' is a fragment, and the intent (checking that a product fits a shelf) has to be reconstructed from the title and from parameter names like shelfDepthCm and frontClearanceCm. It does identify the exact product, which distinguishes it from siblings like tds_purchase_m_lodge_deluxe_pan_scraper, but the operation itself is left implicit.

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?

The only guidance is about how to populate offeredModel ('seller's model field or exact variant name') and that measurements must be for the exact variant. There is no statement of when this tool should be called instead of a related one such as tds_quote_storage_space, nor any precondition about which measurements the agent must obtain first.

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.