Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · SodaStream Classic

tds_purchase_m_sodastream_classic
Read-onlyIdempotent

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

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, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds only the reminder that clearances must be included in the measurements; it does not disclose what the tool returns, what a failed fit means, or whether any validation errors are raised.

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 filler, but the opening fragment "Recorded model Classic" is cryptic and occupies the front-loaded position where the actual operation should be stated. The remaining content is efficient but arrives before the agent knows what the tool does.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter, all-required tool with no schema descriptions and no output schema, the description is thin: it gives entry rules for the model and measurements but never explains the outcome (a fit verdict?) or the units. The annotation set covers safety, so the gap is mainly about return meaning rather than risk.

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% across five required parameters, so the description must carry the load. It does clarify that offeredModel should mirror the seller's model field or exact variant name, and that the four measurement fields must describe the exact variant including required clearances, which is genuinely useful. It still leaves useClearanceCm vs frontClearanceCm and the cm units implicit.

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?

The description opens with "Recorded model Classic," which restates the tool name rather than stating what the tool does. It never says the tool checks whether the SodaStream Classic fits a shelf/space, despite the title hinting at it, so the agent must infer the operation from the title and sibling tds_quote_storage_space.

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?

"Use the seller's model field or exact variant name" is parameter-entry guidance, not when-to-use guidance. There is no statement of when this tool should be chosen over the many other tds_purchase_m_* variants or over tds_quote_storage_space.

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.