Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · SodaStream FRESH PLUS

tds_purchase_m_sodastream_fresh_plus
Read-onlyIdempotent

Recorded model FRESH PLUS. 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_fresh_plus"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

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=true, idempotentHint=true, destructiveHint=false and closed-world scope, so the safety profile is covered. Beyond that the description adds nothing behavioral: it does not say whether a fit verdict is produced, how clearances are applied, or what happens when measurements fall short.

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 little padding, but the opening 'Recorded model FRESH PLUS' mostly restates the tool name rather than front-loading the action. The remaining two sentences are terse to the point of omitting the core verb.

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 five-parameter, all-required tool with no output schema and no parameter descriptions needs the description to explain what a call produces and how the measurements combine. The definition supplies neither, so an agent cannot tell the output or the fit logic from the text.

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% for all five required numeric parameters, so the description carries the full burden. It clarifies offeredModel (seller's field or exact variant name) and that clearances must be included, but leaves shelfDepthCm, productDepthCm, useClearanceCm and frontClearanceCm pairwise distinctions and their units 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 names the recorded model (FRESH PLUS) but never states the action — presumably validating that this appliance fits the kitchen space, though that verb only appears in the title. The agent can identify which product variant this covers, but not clearly what the tool does with the measurements it accepts.

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?

There is guidance on how to source values ('use the seller's model field or exact variant name') but no statement of when to call this tool versus alternatives such as tds_quote_storage_space or the other SodaStream variants. No preconditions or exclusions are given.

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.