Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · VASAGLE Höhenverstellbare Ablage mit Steckdose fürs Wohnzimmer

tds_purchase_m_vasagle_vasagle_hoehenverstellbare_a_555884a5
Read-onlyIdempotent

Recorded model Höhenverstellbare Ablage mit Steckdose fürs Wohnzimmer. 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_hoehenverstellbare_a_555884a5"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds only that the variant and clearances must match exactly, and says nothing about what the call yields (a fit verdict?) or how the clearance is applied. For a computation tool with no output schema, that is a real gap but not a contradiction.

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, front-loaded, with no filler prose. However, the opening sentence 'Recorded model Höhenverstellbare Ablage...' largely restates the tool's model binding and title without adding decision value, while the more important dimension semantics go unaddressed.

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?

An 8-required-parameter geometry tool with zero schema coverage and no output schema needs the description to explain the item-vs-interior pairing, padding semantics, and the returned verdict. None of these are covered, so an agent could easily swap item and inner dimensions and get a wrong fit result.

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 semantics and mostly does not. It clarifies offeredModel (seller's model field or exact variant name) and hints that paddingCm is the 'required clearances', but it never explains the crucial itemWidthCm/DepthCm/HeightCm versus innerWidthCm/DepthCm/HeightCm distinction, nor whether padding is per side or total.

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 identifies the resource (the recorded VASAGLE model and its variant measurements) but never states the action in a verb: it never says the tool checks whether the item fits inside the given interior space. The title 'Check storage fit' carries that meaning, but the description body alone leaves the operation implied rather than stated, and nothing distinguishes it from the many sibling tds_purchase_m_* tools.

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?

It gives concrete input guidance: use the seller's model field or exact variant name, and use measurements for the exact variant including required clearances. That tells the agent how to supply values, but there is no when-to-use vs when-not framing and no named alternative for a different kind of fit or clearance question.

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.