Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Hario Tea Pot Chanomaru

tds_purchase_m_hario_tea_pot_chanomaru
Read-onlyIdempotent

Recorded model Tea Pot Chanomaru. 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_hario_tea_pot_chanomaru"
  }
}

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?

The annotations already declare read-only, idempotent, non-destructive, closed-world behavior, and the description does not contradict them. The description adds only the requirement to include required clearances; it does not explain the result, validation behavior, or units, which leaves clear gaps.

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?

The description is compact and avoids unnecessary detail, with three short sentences. Its structure is not ideal because the first sentence restates the product name rather than front-loading the purpose, but there is little wasted wording.

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-parameter tool with no output schema and no schema descriptions, the definition is incomplete: it does not explain the fit-check outcome or define the dimensions and clearances. The annotations cover safety, but the description still leaves substantial invocation ambiguity.

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 parameter meaning. It partially explains offeredModel via the seller’s model field or exact variant name and mentions required clearances, but it does not define shelfDepthCm, productDepthCm, useClearanceCm, or frontClearanceCm individually, leaving four of five parameters ambiguous.

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 ('Tea Pot Chanomaru') and implies a fit/clearance check through the measurement wording, but it never states the action explicitly. 'Recorded model' largely restates the product/title, so an agent must infer the kitchen-space check from the title.

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?

It gives input-selection advice: use the seller’s model field or exact variant name, and use measurements for the exact variant including required clearances. It does not explicitly say when to use this tool versus sibling product tools or when not to use it, so the guidance is implied rather than complete.

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.