Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · SodaStream E-DUO

tds_purchase_m_sodastream_e_duo
Read-onlyIdempotent

Recorded model E-DUO. 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_e_duo"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/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 openWorldHint=false, so the safety profile is covered. Beyond that the description discloses nothing: not what gets persisted, not what the caller learns back (a fit verdict?), and "Recorded model" is vague enough to be read as a write when annotations say read-only. No output schema exists to fill the gap.

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?

Two short sentences with no padding, but the structure is poor: it opens with a sentence fragment rather than the purpose. Brevity here reflects under-specification rather than tight writing.

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?

Five required parameters, no output schema, and no annotations about results leave the description too thin. An agent cannot tell what the tool returns or what a successful call establishes about whether the E-DUO fits the kitchen space.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 parameters, so the description must carry the load. It only loosely gestures at two groups — the model identifier and the clearance measurements — without distinguishing shelfDepthCm from productDepthCm or useClearanceCm from frontClearanceCm, or stating the unit convention beyond what the names imply.

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 E-DUO" is a fragment restating the tool name rather than a verb+resource statement. The description never says what the tool actually does — presumably record kitchen measurements against the E-DUO to check fit, per the title — so an agent must infer the action from the title and parameter names alone.

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?

It gives value-selection guidance ("use the seller's model field or exact variant name", "measurements for the exact variant") but no when-to-use vs. when-not framing. It never references alternatives such as the E-Terra sibling or tds_quote_storage_space, nor any prerequisite for invoking it.

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.