Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Lodge Camp Dutch Oven

tds_purchase_m_lodge_camp_dutch_oven
Read-onlyIdempotent

Recorded model Camp Dutch Oven. 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_camp_dutch_oven"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds nothing beyond that: it never says the tool evaluates fit/pass-fail, what happens when measurements fail the check, or how clearances are applied, which is the core behavior an agent needs to know.

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?

It is short and wastes no space on padding, but it is front-loaded with a low-value fragment ("Recorded model Camp Dutch Oven") and spends its remaining sentences on input hints rather than purpose. Terse, but not efficiently organized around what the agent most needs.

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 required parameters at 0% schema coverage, no output schema, and only annotations for the safety profile, the description should explain the fit-check result and the meaning of each measurement. It leaves the return behavior and most parameter semantics undocumented, which is inadequate for a five-input validation tool.

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 load. It hints that offeredModel should come from the seller's model field or exact variant name, but it never explains the distinction between shelfDepthCm, productDepthCm, useClearanceCm, and frontClearanceCm, nor units or measurement basis.

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?

"Recorded model Camp Dutch Oven" restates the product name rather than stating what the tool does; the actual action (checking whether the oven fits a kitchen space) is only inferable from the title, not the description. No sibling is named or distinguished, so an agent cannot tell this apart from tds_quote_storage_space or the other purchase tools.

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 instructions ("use the seller's model field or exact variant name", "use measurements for the exact variant") are parameter-input hints, not when-to-use guidance. Nothing says when to invoke this versus a storage-quote or plain purchase tool, and no exclusions or prerequisites 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.