Skip to main content
Glama

The Doll Scout Home Tools

Check bathroom mounting clearance · VASAGLE Badezimmerschrank mit offenen Fächern

tds_purchase_m_vasagle_vasagle_badezimmerschrank_mi_7230133c
Read-onlyIdempotent

Recorded model Badezimmerschrank mit offenen Fächern. 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>",
      "availableWidthCm": "<availableWidthCm>",
      "availableHeightCm": "<availableHeightCm>",
      "mountedWidthCm": "<mountedWidthCm>",
      "mountedHeightCm": "<mountedHeightCm>",
      "serviceMarginCm": "<serviceMarginCm>"
    },
    "name": "tds_purchase_m_vasagle_vasagle_badezimmerschrank_mi_7230133c"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
mountedWidthCmYes
mountedHeightCmYes
serviceMarginCmYes
availableWidthCmYes
availableHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/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. The description adds that evaluation is against the recorded model data and must be variant-exact, but says nothing about what is computed or how a mismatch/clearance failure is surfaced.

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 with no padding, but the lead sentence is a near-verbatim restatement of the product/title and carries no operational information. The useful instructions (model field, exact variant, clearances) are buried in the trailing sentences.

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?

A six-required-parameter clearance calculation with zero schema documentation and no output schema needs more than three sentences. Missing are units confirmation, the meaning of each dimension pair, how serviceMargin affects the result, and what the response indicates, leaving an agent to guess at invocation correctness.

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 six required parameters. The description partially compensates by pointing offeredModel at the seller's model field and hinting that the four dimension parameters plus serviceMargin are 'measurements for the exact variant', but it never distinguishes mounted vs available dimensions or explains what serviceMargin represents.

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 'Recorded model Badezimmerschrank mit offenen Fächern', which restates the product name rather than stating an action. Only the fragment 'including required clearances' hints that this is a fit/clearance check; the actual verb and outcome live in the title, not the description, so the tool's purpose must be inferred.

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?

'Use the seller's model field or exact variant name' and 'Use measurements for the exact variant' give real input constraints that imply usage. However, there is no statement of when this tool should be chosen over another variant tool, nor any exclusion or precondition beyond the exactness constraint.

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.