Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Kuhn Rikon Auto Safety Master Opener

tds_purchase_c08
Read-onlyIdempotent

Recorded model 24278. 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_c08"
  }
}

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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one real behavioral constraint: measurements must correspond to the exact offered variant and must include required clearances, otherwise the check is invalid. It says nothing about what the tool returns (fit verdict? failure reasons?) or how mismatched models are handled.

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?

Three short sentences with no padding, which is good. But the lead sentence 'Recorded model 24278' front-loads an unexplained catalog fact rather than the tool's action, and the remaining sentences are terse to the point of being cryptic.

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?

Five required parameters with zero schema descriptions, no output schema, and no annotations covering semantics. For a fit/clearance evaluation tool the description should explain what the five measurements mean and what the outcome represents; it does neither, leaving an agent unable to interpret results or supply correct front vs use clearances.

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%, so the description must carry semantics, and it partially does: it maps the model parameter to the seller's model field / exact variant name and signals that clearance measurements must be included. However, it never separates shelfDepthCm from productDepthCm or useClearanceCm from frontClearanceCm (two conceptually different clearances), nor does it define units beyond the parameter-name suffix.

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 title says 'Check kitchen space' for a specific Kuhn Rikon opener, and the description hints at variant matching plus clearances, so the domain is inferable. But the description never states the actual operation (verifying whether a variant fits given shelf, product and clearance measurements) or what the result means. With an opaque name like tds_purchase_c08 and 30+ opaque siblings, an agent must 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?

The two sentences are input-fidelity instructions ('use the seller's model field or exact variant name', 'measurements for the exact variant'), not tool-selection guidance. There is no statement of when to use this versus tds_quote_storage_space or the other tds_purchase_* tools, and no preconditions or exclusion cases.

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.