Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Zojirushi Stainless Mug SU-BA36/48

tds_purchase_m_zojirushi_suba
Read-onlyIdempotent

Recorded model Stainless Mug SU-BA36/48. 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_suba"
  }
}

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds a genuine correctness constraint — measurements must be for the exact variant including required clearances — but says nothing about what the call returns (fit verdict? margin?) despite there being no output schema.

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?

Two sentences with no wasted words, but the space is spent on input-sourcing hints rather than front-loading the purpose. It is concise to the point of under-specification rather than genuinely well-structured.

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 all-required, zero-documented numeric parameters and no output schema, the definition should explain what the measurement inputs mean relative to each other and what result the agent gets back. Neither is present, so the agent cannot reliably predict the outcome of a correct call.

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 required parameters, and it does not. It gestures at the model field and at 'measurements ... including required clearances,' but never distinguishes productDepthCm from shelfDepthCm or useClearanceCm from frontClearanceCm — exactly the ambiguity an agent would trip on.

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 opens with 'Recorded model Stainless Mug SU-BA36/48,' which identifies the product but never states the operation. Only the title ('Check kitchen space') implies a fit/clearance evaluation; the description itself never says what the tool computes or returns, so an agent must infer the verb.

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 about sourcing inputs ('use the seller's model field or exact variant name'), not about when to call this tool versus the many sibling Zojirushi/Klean Kanteen mug tools or tds_quote_storage_space. There are no exclusions, prerequisites, or alternative-routing 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.