Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · VASAGLE Schwebende Nachttische mit Schublade

tds_purchase_m_vasagle_vasagle_schwebende_nachttisc_6dfeabb5
Read-onlyIdempotent

Recorded model Schwebende Nachttische mit Schublade. 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_schwebende_nachttisc_6dfeabb5"
  }
}

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 readOnly=true, idempotent=true, destructive=false and a closed-world scope, so safety is covered. The description adds almost nothing beyond that: it doesn't say what a call yields (fit verdict, clearance check, quote?), how padding influences the result, or how inner vs. outer measurements are used — the key behavior for a fit-check tool.

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?

The text is short and the instructions are front-loaded, but the first sentence ('Recorded model ...') is largely redundant with the tool name and title, spending one of only two sentences on restatement rather than missing semantics.

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?

For an 8-required-parameter geometric fit tool with no output schema and no per-parameter documentation, the description does not supply enough for an agent to invoke it correctly — clearances, units assumptions, and the meaning of inner dimensions are all left to guesswork.

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 full explanatory burden. It only gestures at two of them ('seller's model field or exact variant name' for offeredModel, 'required clearances' for paddingCm) and leaves the item vs. inner width/depth/height distinction — the core semantic of this tool — completely unexplained.

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 never states a verb describing what the tool does — it opens with 'Recorded model Schwebende Nachttische mit Schublade', which restates the product rather than an action. Only by combining the title ('Check storage fit') and the measurement guidance can an agent infer that this evaluates whether the item/variant fits. It also does not differentiate itself from siblings such as tds_quote_storage_space or tds_accessory_fit_through_lip.

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' and 'Use measurements for the exact variant' give input-sourcing guidance, but there is no statement of when to call this tool versus the many other per-product siblings or the quote/fit tools. No exclusions, no prerequisites, no outcome expectations.

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.