Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Hario Tea Pot Asanoha

tds_purchase_m_hario_tea_pot_asanoha
Read-onlyIdempotent

Recorded model Tea Pot Asanoha. 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_asanoha"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/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. The description adds nothing behavioral beyond that: it says nothing about what the result means, whether a failed fit is an error or a value, or what happens when measurements conflict with the recorded model.

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, so it is not bloated, but the leading sentence "Recorded model Tea Pot Asanoha" carries almost no actionable information and delays the one substantive instruction. The parameter guidance is packed into two dense clauses rather than being structured per input.

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?

This is a five-parameter, all-required tool with no schema descriptions and no output schema, so the description should explain the five inputs and what the tool reports back. It covers the inputs only at a high level and never tells the agent what a successful result looks like, leaving a substantial burden unaddressed.

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%, so the description must carry the semantics. It does clarify that offeredModel should come from the seller's model field or exact variant name, and that the numeric inputs are measurements for the exact variant including required clearances, but it never distinguishes shelfDepthCm from productDepthCm or explains how useClearanceCm and frontClearanceCm combine.

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 Tea Pot Asanoha," which mostly restates the title rather than stating a verb, but the second sentence's instruction to supply the variant's measurements including clearances implies a fit/space-check operation. An agent can infer the domain from the title plus this text, yet no sentence says plainly that the tool evaluates whether the teapot fits a shelf.

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 present ("use the seller's model field or exact variant name") concerns how to fill a parameter, not when to select this tool. There is no mention of when not to use it or of the variant-specific sibling tds_purchase_m_hario_tea_pot_chanomaru, which an agent could easily confuse with this one.

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.