Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · HARIO V60 Ceramic Dripper 02

tds_purchase_c07
Read-onlyIdempotent

Recorded model VDC-02W. 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_c07"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 fully covered and the description rightly doesn't repeat it. The description adds that clearances are required and that inputs must match the exact variant, which is genuinely useful behavioral context. However, it never says what a call produces — fit verdict, error, warning — and there is no output schema to fall back on.

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 the recorded model ID front-loaded, then input guidance, then measurement guidance. There is no filler. It is tight, though the front-loading is on a model code rather than on what the tool does.

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 read-only fit-check with five required numeric inputs and no output schema, the description never discloses the result shape or what counts as a pass/fail, leaving the agent unable to predict the response. It also omits units, which the parameter names only weakly imply (cm). Actionable input rules are present, but the return-side completeness is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 carries the burden and does partially meet it: it maps "seller's model field or exact variant name" to offeredModel and "measurements for the exact variant, including required clearances" to the depth and clearance parameters. It does not clarify what each clearance means directionally (use versus front) or how shelf depth and product depth interact. Partial compensation justifies 3, not higher.

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 opens with "Recorded model VDC-02W" and talks about model fields, variant names, and measurements, but never states the action: it does not say it checks whether a dripper fits on a shelf or produces a fit verdict. The tool's purpose must be inferred from the title "Check kitchen space", which the description itself does not restate. The model/variant guidance is useful but is about correct input selection rather than what the tool does.

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 real input-selection guidance: "Use the seller's model field or exact variant name" and "Use measurements for the exact variant, including required clearances," which helps disambiguate among many per-product siblings. What it does not provide is when to call this tool versus when not to, or any precondition such as needing the product in hand and a shelf measured. Usage is implied rather than 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.