Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Lodge Grill Presses

tds_purchase_m_lodge_grill_press
Read-onlyIdempotent

Recorded model Grill Presses. 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_press"
  }
}

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only that measurements must correspond to the exact variant and include required clearances; it says nothing about what the check evaluates or how a failure is reported, which is the behavior an agent would actually need.

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?

Three short sentences, front-loaded with the resource, then the model-identification rule, then the measurement rule. No filler; the brevity is offset by under-specification captured in other dimensions rather than padding.

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 geometric inputs, no output schema, and 0% schema description coverage, the description should explain what a successful check returns and how the clearance figures are compared against shelf depth. It leaves the agent guessing whether the result is a boolean fit, a clearance margin, or a recommendation, which is a substantial gap for a decision-support 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 numeric parameters, so the description carries the full burden. It loosely maps offeredModel to "seller's model field or exact variant name" and gestures at the four measurement fields via "measurements for the exact variant, including required clearances," but gives no units, no measuring convention (internal vs external depth), and no distinction between useClearanceCm and frontClearanceCm.

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?

"Recorded model Grill Presses" names the resource but no verb, and only the title ("Check kitchen space") reveals that this is a fit/clearance assessment rather than a purchase or lookup. It implicitly distinguishes itself from the other Lodge product tools by dealing with a specific recorded model plus space measurements, but the agent must infer that from the schema fields.

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" tells the agent how to populate one parameter, not when this tool is the right one to call versus the sibling product tools or a storage-space tool. There are no when-to-use, when-not-to-use, or alternative-selection statements.

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.