Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · SodaStream FOUNTAIN - Reward

tds_purchase_m_sodastream_fountain_loyalty
Read-onlyIdempotent

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

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, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing behavioral beyond that — no note on what is validated, what a failed check looks like, or whether results are persisted.

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 padding, which is structurally fine. However, the brevity is achieved by omitting substance rather than by eliminating redundancy, so it reads as under-specified rather than tight.

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?

A five-required-parameter tool with zero schema coverage and no output schema needs the description to explain units, the depth-minus-clearance relationship, and expected result. None of that is present, so an agent must guess how to supply measurements for an unfamiliar variant.

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 numeric parameters, so the description must carry the load. It only gestures at offeredModel (seller's model field / exact variant name) and at clearances, leaving shelfDepthCm versus productDepthCm, the cm units, and the relationship between product depth plus clearance and shelf depth entirely unexplained.

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 restates the product identity ("Recorded model FOUNTAIN - Reward") but never states the action the tool performs — presumably validating that this variant fits available kitchen space. Only the title ("Check kitchen space") conveys the verb, so an agent reading the description alone cannot tell what calling it does.

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") but no when-to-use condition, no prerequisites, and no differentiation from the many sibling tds_purchase_m_* variant tools. It is implied that this is the per-variant space check, but that is never 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.