Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Thermos 12oz Double Wall Tumbler

tds_purchase_m_thermos_12oz_double_wall_tumbler
Read-onlyIdempotent

Recorded model 12oz Double Wall Tumbler. 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_thermos_12oz_double_wall_tumbler"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/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 without the description. The description adds that measurements must correspond to the exact variant and must include required clearances, which is real behavioral context, but it never says what the call returns (pass/fail fit verdict, stored record) or what happens when clearances are insufficient.

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?

Only two short sentences, so nothing is padded, but the opening sentence is a product restatement that spends the prime position on information already in the name and title, pushing the only actionable guidance into the tail.

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?

A five-required-parameter tool with zero schema descriptions and no output schema needs the description to define the measurement inputs and the outcome; instead the description is three terse clauses. An agent knows to supply variant-accurate measurements but not the units semantics or what a successful response means.

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 and largely fails to. It maps loosely onto offeredModel ("seller's model field or exact variant name") and groups the rest as "measurements ... including required clearances", but never explains how shelfDepthCm, productDepthCm, useClearanceCm and frontClearanceCm differ or are compared.

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 12oz Double Wall Tumbler" restates the product/title rather than stating a verb and outcome; the actual operation (recording a candidate model and validating shelf fit) is only inferable from the title "Check kitchen space" and the mention of clearances. An agent cannot tell from the description alone whether this writes a record, computes a fit verdict, or both.

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 "Use the seller's model field or exact variant name", which addresses input selection, not when to use this tool. There is no statement of when a fit check is required, what to do when it fails, or how this product-specific tool relates to sibling product tools or to tds_quote_storage_space.

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.