Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Hario Beaker Beer Mug, 500mL

tds_purchase_m_hario_beaker_beer_mug_500ml
Read-onlyIdempotent

Recorded model Beaker Beer Mug, 500mL. 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_beaker_beer_mug_500ml"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. Beyond that the description adds only that measurements must reflect the exact variant and its required clearances; it does not say whether the call returns a fit/no-fit verdict, what happens with variant mismatches, or whether anything is persisted.

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 padding, but the opening sentence is essentially the product name repeated and therefore earns little of its space. The more useful instruction about exact-variant measurements comes second rather than being front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five required parameters at 0% schema coverage and no output schema, the definition should clarify both the parameter meanings and what the call produces. It addresses the variant/clearance idea but leaves an agent guessing how the four dimensions are measured and what result to expect, which is too thin for a tool this parameter-heavy.

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 carries the full burden. It maps loosely onto offeredModel ('seller's model field or exact variant name') and gestures at the four numeric fields via 'measurements ... including required clearances', but it never distinguishes shelfDepthCm from productDepthCm or explains what useClearanceCm and frontClearanceCm mean or what units are expected.

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 mainly restates the product identity ('Recorded model Beaker Beer Mug, 500mL') rather than naming an action. Only the second sentence hints at the real function (checking shelf fit via measurements and clearances), and even that is framed as input advice rather than a statement of what the tool does. The title ('Check kitchen space') carries more purpose information than the description does.

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 given is about how to fill parameters ('use the seller's model field or exact variant name', 'use measurements for the exact variant'), not about when to choose this tool. There is no indication of how it relates to siblings such as tds_quote_storage_space or the other product-specific purchase tools, and no prerequisites or exclusions are 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.