Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · SodaStream FOUNTAIN

tds_purchase_m_sodastream_fountain
Read-onlyIdempotent

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

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 covered without the description. The description adds that the check is clearance-based for the exact variant, but says nothing about the outcome (pass/fail, margin, error when clearances are too tight) and there is no output schema to fill that gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with no filler, and the model-identification constraint is front-loaded. The telegraphic style is efficient but at times reads as shorthand rather than a complete instruction.

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?

For a five-parameter, fully-required validation tool with no output schema and no parameter documentation, the description should explain how the measurements combine and what the caller gets back. Instead it leaves both the numeric semantics and the result of the check unspecified, so an agent cannot confidently construct a correct call.

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 five required parameters, so the description carries the full burden, yet it only vaguely gestures at them: offeredModel via "seller's model field or exact variant name" and the four numeric fields via "measurements ... including required clearances". It never distinguishes shelfDepthCm from productDepthCm, or useClearanceCm from frontClearanceCm, leaving the agent to guess units and which measurement goes where.

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 identifies the exact product variant ("Recorded model FOUNTAIN") but never states the operation — combined with the title it reads as a clearance/fit check, yet the description alone says nothing about validating shelf space. It does at least pin down which variant is in scope, which is the main thing separating it from the many sibling product tools.

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?

It gives useful sourcing guidance ("Use the seller's model field or exact variant name", "Use measurements for the exact variant, including required clearances"), which implies the caller must supply variant-accurate data. It never says when to choose this tool over a sibling such as tds_quote_storage_space, nor what to do when the variant is unknown.

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.