Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · SodaStream TERRA

tds_purchase_m_sodastream_terra
Read-onlyIdempotent

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

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed world, so the safety profile is fully covered. The description adds one behavioral point beyond them - that measurements must cover the exact variant including required clearances - but says nothing about what the call returns or whether a fit verdict is produced, which matters 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.

Conciseness4/5

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

Three short sentences with no filler, and the model-selection constraint is front-loaded. The opening sentence is the weakest, spending space restating the model rather than the action.

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?

With five required, undocumented parameters, no output schema, and no explanation of the returned result, the definition leaves an agent unsure how to populate the clearance fields and what to expect back. For a measurement-driven evaluation tool, more specification is required.

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 carry the load. It clarifies offeredModel and broadly says to use variant-specific measurements including clearances, but never distinguishes shelfDepthCm from productDepthCm or useClearanceCm from frontClearanceCm, leaving half the parameters ambiguous.

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?

"Recorded model TERRA" largely restates the tool name/model rather than stating a verb+outcome. The follow-on sentences hint that the tool evaluates a variant against kitchen measurements, but the description never explicitly says it checks whether the appliance fits the shelf/space, so an agent must infer the operation from the title.

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 description gives input-selection guidance (use the seller's model field or exact variant name) but no when-to-use versus alternatives, despite siblings such as tds_quote_storage_space and the other per-model purchase tools. There are no exclusions or preconditions stated.

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.