Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · SodaStream FRESH

tds_purchase_m_sodastream_fresh
Read-onlyIdempotent

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

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. Beyond that, the description only hints that the exact variant matters; it does not say what happens when the model string does not match a recorded variant, whether clearances are validated against a rule, or what the caller receives back — notable since there is no output schema.

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 the least informative part and is front-loaded, while the genuinely useful constraint (exact variant, include clearances) is buried at the end. Efficient in length, weak in ordering.

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, fully required tool with 0% schema coverage and no output schema needs a description that explains inputs and the result; this one supplies neither the depth-measurement distinction nor the returned fit outcome. An agent could not confidently construct a correct call from the definition alone.

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 five required parameters, so the description must compensate and largely does not. It gestures at offeredModel ("seller's model field or exact variant name") and at clearances collectively, but never explains the distinction between shelfDepthCm and productDepthCm, nor how useClearanceCm and frontClearanceCm combine into a fit decision.

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 FRESH" restates the name/title rather than stating what the tool does — there is no verb indicating whether it records, validates, or checks dimensions against a fit. The title carries the actual purpose ("Check kitchen space"), so the description adds nothing an agent could not read from the title alone, and it does not distinguish FRESH from FRESH Plus, Classic, Terra, etc.

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 sentences "Use the seller's model field or exact variant name" and "Use measurements for the exact variant" are input conventions, not when-to-use guidance. There is no statement of when this tool applies versus sibling variants or versus a generic storage-space quoting tool, and no exclusions or preconditions beyond an implied exact-variant requirement.

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.