Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · VASAGLE Beleuchteter Badkomfort

tds_purchase_m_vasagle_vasagle_beleuchteter_badkomf_6fcbf3aa
Read-onlyIdempotent

Recorded model Beleuchteter Badkomfort. 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>",
      "itemWidthCm": "<itemWidthCm>",
      "itemDepthCm": "<itemDepthCm>",
      "itemHeightCm": "<itemHeightCm>",
      "innerWidthCm": "<innerWidthCm>",
      "innerDepthCm": "<innerDepthCm>",
      "innerHeightCm": "<innerHeightCm>",
      "paddingCm": "<paddingCm>"
    },
    "name": "tds_purchase_m_vasagle_vasagle_beleuchteter_badkomf_6fcbf3aa"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/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 covered. Beyond that, the description only adds a determinism constraint about using the exact variant and clearances; it does not say what the tool returns (fit verdict, margin, pass/fail), how clearances are applied, or what happens with a mismatched model — with no output schema to fall back on, this is a notable 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?

Two short sentences with no filler, so it is not verbose. However, it is front-loaded with the product name rather than the action, and the sentences are terse to the point of under-specification rather than crisp guidance.

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 an 8-parameter, all-required numeric computation tool with no output schema and no enum hints. A complete definition would pin down units, item-vs-inner semantics, padding, and the shape of the result; the description supplies none of these, so an agent must guess at core inputs before it can call the tool correctly.

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 8 required parameters, so the description must carry the load. It only gestures at two things: offeredModel (use the seller's model field or exact variant name) and the measurement/padding group ("measurements for the exact variant, including required clearances"). It never explains the critical distinction between itemWidth/Depth/HeightCm and innerWidth/Depth/HeightCm, the units, or what paddingCm is added to, leaving most parameters semantically undocumented.

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 title says "Check storage fit" and the description says "Use measurements for the exact variant, including required clearances," which together imply a fit/capacity check for a specific VASAGLE bathroom cabinet. However, the description itself never states a verb+resource like "checks whether the item fits inside the given inner dimensions"; it opens with "Recorded model Beleuchteter Badkomfort," which is a catalog identifier rather than a purpose statement. The intent is inferable but not explicit, and nothing distinguishes it from fit-oriented siblings.

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?

"Use the seller's model field or exact variant name" is guidance on how to fill the offeredModel parameter, not guidance on when to invoke this tool. There is no statement of when this tool applies versus alternatives such as tds_accessory_fit_through_lip, tds_threshold_storage_totes, or tds_quote_storage_space, and no exclusions or prerequisites beyond exact-variant matching.

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.