Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Zojirushi Stainless Mug SM-SHE48ZA

tds_purchase_m_zojirushi_stainless_mug_sm_she48za
Read-onlyIdempotent

Recorded model Stainless Mug SM-SHE48ZA. 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_zojirushi_stainless_mug_sm_she48za"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's remaining job is to explain what the check does and what the result means. It only mentions that required clearances must be supplied and adds nothing about how fit is determined, what the response indicates, or how clearance values affect the outcome.

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 'Recorded model Stainless Mug SM-SHE48ZA' is front-loaded meta-commentary rather than the purpose, and the phrasing is slightly stilted. It is compact but not optimally ordered.

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 five-required-parameter computational tool with no parameter descriptions and no output schema, the description is too thin: it leaves the agent unsure what is being computed and how each measurement feeds the result. The variant identification is covered, but the mechanics of the space check are not.

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% for five required numeric parameters, so the description must carry the semantics. It gestures at 'measurements' and 'required clearances' but never distinguishes shelfDepthCm, productDepthCm, useClearanceCm, or frontClearanceCm, nor states units or what 'use clearance' 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 identifies the exact product variant (SM-SHE48ZA) and alludes to measurement-based checking via 'Use measurements for the exact variant, including required clearances,' but never states the actual operation or outcome (e.g., 'determines whether the mug fits on your shelf'). The real verb lives only in the title 'Check kitchen space', so an agent must infer purpose from the title and the parameter names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/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' and 'Use measurements for the exact variant' give input-selection guidance and implicitly steer the agent to the right variant among the many sibling mug tools. However, no explicit when-to-use vs. alternatives guidance (e.g., when to prefer tds_quote_storage_space) and no preconditions 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.