Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Hario Water Dripper Pota N

tds_purchase_m_hario_water_dripper_pota_n
Read-onlyIdempotent

Recorded model Water Dripper Pota N. 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_water_dripper_pota_n"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds nothing behavioral beyond that: it does not say what the check computes, what verdict or data is returned (no output schema exists), or how the clearance figures are used.

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 sentences with no filler, so it is concise. However, the lead sentence is a model note rather than an actionable statement, so the structure is neither informative nor properly front-loaded for a task tool.

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, fully-required tool with no output schema demands the description explain what is evaluated and how the measurement inputs combine. Instead the description is vague about both, leaving the agent unable to predict the result or distinguish the individual measurement fields.

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% for five required parameters. The description only weakly glosses 'offeredModel' ('seller's model field or exact variant name') and lumps the rest into 'measurements ... including required clearances', leaving shelfDepthCm, productDepthCm, useClearanceCm and frontClearanceCm indistinguishable to the agent.

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 what the tool does. 'Recorded model Water Dripper Pota N' restates the entity and reads as a data note, not an action. The actual purpose (checking kitchen/shelf space fit) is only inferable from the title, and no sibling differentiation is offered among the many tds_purchase_m_* product tools.

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 only instructions concern parameter sourcing ('Use the seller's model field or exact variant name', 'Use measurements for the exact variant'), not when to invoke this tool versus alternatives. There is no when-to-use, when-not-to-use, or prerequisite 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.