Skip to main content
Glama

The Doll Scout Home Tools

Check bathroom mounting clearance · VASAGLE Badezimmerschrank mit Beleuchtung und Ablagen

tds_purchase_m_vasagle_vasagle_badezimmerschrank_mi_453106d8
Read-onlyIdempotent

Recorded model Badezimmerschrank mit Beleuchtung und Ablagen. 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>",
      "availableWidthCm": "<availableWidthCm>",
      "availableHeightCm": "<availableHeightCm>",
      "mountedWidthCm": "<mountedWidthCm>",
      "mountedHeightCm": "<mountedHeightCm>",
      "serviceMarginCm": "<serviceMarginCm>"
    },
    "name": "tds_purchase_m_vasagle_vasagle_badezimmerschrank_mi_453106d8"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
mountedWidthCmYes
mountedHeightCmYes
serviceMarginCmYes
availableWidthCmYes
availableHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. Beyond that the description says nothing about what the check produces (pass/fail clearance result?), what happens when the model is unknown, or how the clearance comparison is computed — and there is no output schema to fill that gap.

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?

Three short sentences, but the first is a near-empty restatement of the model name that consumes front-loaded space without stating an action. The two useful guidance sentences are well ordered, so nothing is bloated, just under-informative.

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 six-required-parameter, zero-coverage, no-output-schema tool needs the description to explain the measurement model and result semantics; instead it covers only model identification. An agent knows what identifies the variant but not what the margins mean or what it gets back.

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% across six required parameters, so the description must compensate and largely fails to. It gestures at a model field and 'measurements ... including required clearances,' but never distinguishes availableWidthCm/availableHeightCm from mountedWidthCm/mountedHeightCm, and never explains serviceMarginCm at all.

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 by naming the recorded model rather than stating an action; the actual purpose (checking mounting clearance for that specific VASAGLE cabinet) must be inferred from the title and the phrase 'including required clearances.' It is not a tautology, but no verb+resource statement appears in the description itself.

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?

'Use the seller's model field or exact variant name' and 'Use measurements for the exact variant' give real input-selection guidance about which model identity to pass. There is no explicit when-to-use vs. sibling checks or statement of what to do if the variant or measurements don't match, so usage remains implied.

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.