Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Zojirushi Stainless Mug SM-ZB48

tds_purchase_m_zojirushi_stainless_mug_sm_zb48
Read-onlyIdempotent

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

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/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 elsewhere. The description adds no behavioral context beyond annotations: it does not say what result is produced, whether mismatched models are rejected, or how clearances 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?

The description is short and free of padding, but it is not front-loaded with the actual operation; it opens with a name restatement instead of the verb, and the two guidance sentences are vague rather than informative.

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 numeric parameters, no output schema, and no documented return semantics, the description should explain what the tool concludes (fit/no-fit) and what the measurement inputs mean. It leaves both unaddressed, so an agent cannot confidently predict the effect of calling it.

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% with five required parameters, so the description carries the full burden and falls short. It vaguely references "the seller's model field" and "measurements ... including required clearances" but never distinguishes shelfDepthCm from productDepthCm, useClearanceCm, or frontClearanceCm, and never states units or how clearances should be derived.

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 Stainless Mug SM-ZB48" restates the name/title rather than stating an operation. There is no explicit verb saying whether this records a product, validates a fit, or checks clearances, so an agent must infer the action from the title alone.

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" gives input guidance, not usage guidance. Nothing explains when this tool should be selected over the many sibling Zojirushi mug variants or over tds_quote_storage_space, and no prerequisites or exclusions are stated.

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.