Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · VASAGLE Schmaler Konsolentisch mit Steckdosen

tds_purchase_m_vasagle_vasagle_schmaler_konsolentis_5144c4d3
Read-onlyIdempotent

Recorded model Schmaler Konsolentisch mit Steckdosen. 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_schmaler_konsolentis_5144c4d3"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior3/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. The description adds a behavioral requirement to use the exact variant and include required clearances, but it does not explain what the tool returns or how fit is determined.

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 description is short and has no obvious filler, but it is not front-loaded with the tool's purpose. The first sentence is a product-name restatement, and the useful input guidance comes only afterward.

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 a tool with eight required parameters, no schema descriptions, and no output schema, the description is too thin. It does not state the operation clearly or explain how the dimension and padding parameters are interpreted, leaving significant gaps for an agent to fill.

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 eight required parameters, so the description must carry the full burden. It only clarifies offeredModel and vaguely refers to measurements and clearances; it does not explain the distinction between itemWidthCm, innerWidthCm, paddingCm, or the other dimension parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a noun phrase, 'Recorded model Schmaler Konsolentisch mit Steckdosen,' which restates the product name rather than stating a specific verb and resource. It never explicitly says the tool checks storage fit, and it does not distinguish this tool from sibling fit or storage 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?

The description gives input constraints ('Use the seller’s model field or exact variant name' and 'Use measurements for the exact variant, including required clearances') but provides no guidance on when to use this tool versus alternatives such as tds_quote_storage_space or tds_accessory_fit_through_lip.

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.