Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · OXO Good Grips 11 lb Stainless Steel Food Scale with Pull Out Display

tds_purchase_c03
Read-onlyIdempotent

Recorded model 11 lb Stainless Steel Food Scale with Pull Out Display. 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_c03"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/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 covered. The description adds that the variant model and its exact measurements including required clearances must be supplied, which is useful context, but it never says what the tool decides or returns (a fit verdict, a failure reason) or how mismatched variants are handled.

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 with the product identity front-loaded and no filler. The phrasing "Recorded model ..." is slightly awkward, but nothing is padded.

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 numeric/string parameters, no output schema, and a spatial-fit computation, the description is far too thin. An agent still cannot tell what the tool returns, what units to use, or what makes a fit succeed or fail.

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 all five parameters. It only gestures at offeredModel ("seller's model field or exact variant name") and vaguely at the clearance parameters ("including required clearances"), and says nothing about shelfDepthCm versus productDepthCm, units, or how clearance values combine with depth.

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 description only identifies the product ("Recorded model 11 lb Stainless Steel Food Scale with Pull Out Display") and never states the operation the tool performs. The action (checking kitchen/shelf space fit) is only recoverable from the title, so the description essentially restates the name/title rather than adding a verb+resource statement.

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" constrains how to fill a field but gives no when-to-use guidance, no conditions under which this tool is preferred over siblings like tds_quote_storage_space, and no exclusions. It is field-filling advice, not tool-selection guidance.

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.