Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Hario Kabuto Coffee Grinder

tds_purchase_m_hario_kabuto_coffee_grinder
Read-onlyIdempotent

Recorded model Kabuto Coffee Grinder. 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_kabuto_coffee_grinder"
  }
}

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the domain constraint that clearance values are required for the exact variant, but says nothing about what the tool evaluates or returns, so it adds only modest value.

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 short, front-loaded sentences with no padding, so it is not verbose. However, the first sentence spends space restating the product name instead of stating the operation, so brevity comes at the cost of information.

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?

A five-parameter, all-required measurement tool with no output schema and no schema descriptions needs the description to define units, the difference between shelf and product depth, and how clearances are applied. None of that is present, leaving the agent to guess at semantics that determine whether the call is correct.

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 numeric parameters, so the description carries the full burden and largely fails it. It gestures at offeredModel and at "measurements ... including required clearances" but never distinguishes shelfDepthCm from productDepthCm, nor useClearanceCm from frontClearanceCm, and gives no units beyond what parameter names imply.

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 never states an action verb for the tool itself; "Recorded model Kabuto Coffee Grinder" largely restates the name/title. Only the phrase about measurements and "required clearances" hints that this is a fit/space check for a specific product variant, and the agent must infer that from the title rather than the text.

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 guidance is about which input value to supply (seller's model field or exact variant name), not about when to choose this tool over siblings such as tds_quote_storage_space or the Kabuto Pro variant. No conditions, prerequisites, or exclusions 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.