Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Hario Harior 7, 600mL

tds_purchase_m_hario_harior_7_600ml
Read-onlyIdempotent

Recorded model Harior 7, 600mL. 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_harior_7_600ml"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by requiring the exact seller model/variant and measurements including clearances, but it does not say what the tool returns or what happens when the item does not fit.

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 short and efficient, with no wasted sentences. It is not front-loaded with the actual action, and it repeats the exact-variant idea, but the overall structure is reasonably clear.

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 schema descriptions, and no output schema, the description is too thin. It does not explain the measurement semantics or the return value sufficiently for an agent to call it confidently without further inference.

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 explain all five required parameters. It only broadly refers to the model/variant field and measurements with clearances, without defining units, distinguishing useClearanceCm from frontClearanceCm, or explaining how shelfDepthCm and productDepthCm are used.

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 product variant and tells the caller to use the seller’s model field and exact measurements, but it never explicitly states the action (checking whether the item fits the kitchen space). The title supplies that context, but the description alone only implies the purpose through the measurement and clearance parameters.

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 description gives input instructions about using the exact variant name and measurements, but it does not explain when to choose this tool over alternatives such as tds_quote_storage_space. There are no exclusions, prerequisites, or explicit when-to-use guidance.

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.