Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · SodaStream E-TERRA

tds_purchase_m_sodastream_e_terra
Read-onlyIdempotent

Recorded model E-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_e_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 the operation read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds that the model must match the exact variant and that clearances are required, but it does not explain what happens with the measurements, whether clearance failures are reported, or what the user should expect as a result.

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?

The description is short, front-loaded with the model identifier, and contains no filler. Its terseness contributes to under-specification, but from a conciseness and structure standpoint it is efficient.

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?

This is a five-required-parameter fit-check tool with no output schema and no parameter descriptions in the schema. The description should explain what the measurements are for, how clearances apply, and what the tool returns or validates; instead it only gives model guidance and a generic clearance instruction, leaving significant gaps.

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%, so the description must compensate for all five parameters. It gives some meaning to 'offeredModel' (seller's model field or exact variant name) and notes that required clearances are needed, but it does not explain the distinctions among 'shelfDepthCm', 'productDepthCm', 'useClearanceCm', and 'frontClearanceCm' or how they should be measured.

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 E-TERRA') and says to use measurements for that variant, which helps distinguish it from sibling product tools. However, it never states the actual operation—checking whether the product fits a kitchen/shelf space—so the purpose is only implied, largely relying on 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?

It gives input guidance ('Use the seller’s model field or exact variant name') and says to use measurements for the exact variant, including required clearances. It does not say when to choose this E-TERRA tool versus sibling variants or versus a general storage-space quote tool, nor does it state any exclusions or prerequisites.

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.