Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · SodaStream CO2-Reservezylinder

tds_purchase_m_sodastream_reserve_co2_kohlensaeure_zylinder
Read-onlyIdempotent

Recorded model CO2-Reservezylinder. 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_reserve_co2_kohlensaeure_zylinder"
  }
}

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 readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety behavior is covered. The description adds no further behavioral context — it does not say what is returned, whether a failing clearance produces an error or a message, or what the recorded result represents. The read-only framing is at least not contradicted, despite the 'purchase' name.

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, so it is compact, but the front-loaded sentence is cryptic rather than informative. Brevity here comes at the cost of meaning rather than from efficient expression.

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 tool with five mandatory numeric parameters, no output schema, and no parameter documentation in the schema, the description leaves far too much unresolved: the outcome of the check, the meaning of the measurements, and the relationship to related tools are all absent.

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 must carry the burden. It only hints that offeredModel comes from the seller's model field and that the measurements describe the exact variant's clearances; it never explains what shelfDepthCm, productDepthCm, useClearanceCm, or frontClearanceCm measure or how they relate.

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 CO2-Reservezylinder,' which largely restates the tool name rather than stating an action. It never says what the tool actually does — verify fit, record a purchase, or compute clearance — and the title ('Check kitchen space') conflicts with the 'purchase' prefix, leaving the agent to guess the verb.

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' and 'Use measurements for the exact variant' are instructions on how to fill inputs, not when to choose this tool over siblings such as tds_quote_storage_space or the other tds_purchase_m_sodastream_* variants. No conditions, exclusions, or alternatives are named.

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.