Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · SONGMICS Runder Sitzhocker mit Stauraum

tds_purchase_m_songmics_songmics_runder_sitzhocker_86eb7ef3
Read-onlyIdempotent

Recorded model Runder Sitzhocker mit Stauraum. 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_songmics_songmics_runder_sitzhocker_86eb7ef3"
  }
}

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, idempotent, non-destructive and closed-world, so safety is covered; the description adds essentially nothing beyond that. It does not say what the tool returns (a pass/fail fit verdict?), whether it validates against a catalog record, or how clearance padding affects the result — the single phrase "including required clearances" is the only behavioral hint.

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 padding or redundancy, but the brevity is under-specification rather than efficiency: the space saved is space an agent needs to know what a fit result means and how inner and outer dimensions differ.

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?

With 8 required parameters, 0% schema coverage and no output schema, the description needs to define the dimension semantics and the returned verdict. It supplies only a model-naming convention and a passing reference to clearances, leaving an agent unable to interpret or trust the measurement inputs.

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 numeric/string parameters, so the description carries the full burden and mostly fails. It clarifies offeredModel (seller's model field or exact variant name) and hints that paddingCm is a required clearance, but leaves the critical item-vs-inner dimension distinction and the meaning of each measurement 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 identifies the product ("Runder Sitzhocker mit Stauraum") and implies a fit check via measurements and clearances, but never states a verb or the outcome produced. The title says "Check storage fit," yet that intent is only inferable from the description, and nothing distinguishes this per-product tool from the many near-identical SONGMICS/VASAGLE 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" and "use measurements for the exact variant" give data-entry guidance for two parameters, but there is no when-to-use/when-not guidance and no routing to alternatives such as tds_quote_storage_space or the other model-specific fit tools. The agent is told how to fill fields, not when to pick this tool.

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.