Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Zojirushi Stainless Mug SM-SF48/60

tds_purchase_m_zojirushi_smsf
Read-onlyIdempotent

Recorded model Stainless Mug SM-SF48/60. 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_smsf"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 measurements must match the exact variant including required clearances, which is useful context, but it says nothing about what happens when clearances are insufficient, what the result looks like, or whether units are enforced.

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 no filler, and the model-identification constraint is placed first. It is telegraphic to the point of dropping a verb, but nothing is wasted.

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?

This is a five-parameter, all-required computation tool with no schema descriptions and no output schema, so the description is the only place an agent can learn how the inputs combine into a verdict. It omits what is returned, how clearance is evaluated, and what distinguishes the depth parameters — substantial gaps for a 'check' tool.

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 burden — and it only partly does. It clarifies offeredModel (seller's model field or exact variant name) and loosely gestures at useClearanceCm/frontClearanceCm as 'required clearances', but leaves shelfDepthCm versus productDepthCm unexplained and gives no unit or measurement-method guidance beyond the '_Cm' suffixes in the parameter names.

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 ('Recorded model Stainless Mug SM-SF48/60') but never states the operation being performed — it relies on the title ('Check kitchen space') to convey that this evaluates fit/clearance. An agent reading only the description would know which model this covers but not what the tool returns or does with the measurements.

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 real input-discipline guidance that implicitly separates the correct variant from the many sibling Zojirushi mug tools. However, there is no explicit when-to-use/when-not statement, no mention of alternatives such as tds_quote_storage_space, and no stated prerequisites.

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.