Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · VASAGLE Schmale Stahlaufbewahrung mit Klappen und Magnetverschluss

tds_purchase_m_vasagle_vasagle_schmale_stahlaufbewa_a1d63662
Read-onlyIdempotent

Recorded model Schmale Stahlaufbewahrung mit Klappen und Magnetverschluss. 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_schmale_stahlaufbewa_a1d63662"
  }
}

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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds no behavior beyond that — nothing about what the returned verdict means, whether padding is added symmetrically, or how mismatches are reported. 'Recorded model' is the only hint that the model is pre-registered, and it is not explained.

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 compact. However, the first sentence spends its space restating the product name rather than stating the operation, so the front-loaded content is the least useful part.

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-parameter, all-required geometry tool with zero schema descriptions and no output schema, the description is far too thin; an agent cannot tell how the dimensions are combined or what a result signifies. Annotations cover safety but not the computational semantics that matter here.

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 burden and largely fails. It does not explain the distinction between item* (outer) and inner* dimensions, does not state that paddingCm is a clearance margin applied per side, and does not give units or valid ranges beyond the schema's numeric bounds.

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 the actual operation (checking whether an item fits a storage unit); it only restates the model name and points at which values to supply. The purpose is inferable from the parameter names (itemWidthCm vs innerWidthCm) and the title, but the description itself gives no verb+resource statement and does not distinguish this tool from the many sibling product-fit tools.

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' are input hints, not when-to-use guidance. There is no indication of when this tool applies versus a sibling product's tool, no prerequisites, and no note on what to do when the variant is unknown.

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.