Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Kinto HIBI fork 190mm

tds_purchase_m_kinto_27106
Read-onlyIdempotent

Recorded model HIBI fork 190mm. 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_kinto_27106"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/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 a closed world, so the safety profile is covered. The description adds a mild correctness constraint (use the exact variant's measurements and its required clearances), but does not explain what the check evaluates or what a pass/fail result means. With annotations present the bar is lower, so this earns a 3 rather than more.

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 filler, but the opening sentence is redundant with the title and consumes the front-loaded position that should carry the tool's purpose. The remaining guidance is terse to the point of under-specification.

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-parameter, fully-required tool with no output schema and no parameter descriptions needs the description to explain the fit calculation and each measurement, but it does neither. An agent can fill the fields but cannot confidently predict what the tool computes or returns.

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 meaning. It only loosely gestures at offeredModel ('seller's model field or exact variant name') and bundles the four numeric fields under 'measurements ... including required clearances', leaving it unclear how shelfDepthCm, productDepthCm, useClearanceCm and frontClearanceCm differ or how they combine.

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 first sentence, 'Recorded model HIBI fork 190mm,' only restates the title's product identifier and never states the actual action (verifying that a product fits available kitchen space). An agent learns which product is involved but not what the tool does with it, and no sibling such as tds_quote_storage_space is contrasted.

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' is a parameter-entry instruction, not a when-to-use rule. There is no statement of when this check is appropriate, what preconditions must hold, or how it differs from the space-quoting sibling.

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.