Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · SodaStream Ultimate Multi-Drink™

tds_purchase_m_sodastream_ultimate
Read-onlyIdempotent

Recorded model Ultimate Multi-Drink™. 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>",
      "shelfDepthCm": "<shelfDepthCm>",
      "productDepthCm": "<productDepthCm>",
      "useClearanceCm": "<useClearanceCm>",
      "frontClearanceCm": "<frontClearanceCm>"
    },
    "name": "tds_purchase_m_sodastream_ultimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

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, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that all five measurements must be for the exact variant "including required clearances," which is modest but real context. It says nothing about what the call produces (a fit verdict?) or how the clearances are used in the evaluation.

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 definition is short and not padded, but the leading sentence is a low-value fragment that repeats the product name, so the useful instruction is not front-loaded. Two sentences carry the actual payload: model identification and measurement sourcing.

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 five required parameters, no output schema, and no annotation describing return behavior, the description should explain what the call reports back (fit/no-fit, margins) and how clearance values are applied. Neither is present, leaving the agent able to call it but not to interpret or trust the result.

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%, and the five required numeric parameters (shelfDepthCm, productDepthCm, useClearanceCm, frontClearanceCm) get no individual explanation. Only offeredModel is clarified (seller's model field or exact variant name), and the phrase "including required clearances" hints that clearance values matter but not how to derive them.

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?

"Recorded model Ultimate Multi-Drink™" is a fragment that restates the product name rather than stating an action; the description never says the tool checks whether the product fits the available shelf space (only the title hints at "Check kitchen space"). An agent can infer it relates to this specific SodaStream model, but the verb and outcome of the operation are absent.

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 guidance given is about how to populate arguments ("use the seller's model field or exact variant name") rather than when this tool applies versus the many other SodaStream variants in the sibling set. No conditions, prerequisites, or alternatives are named.

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.