Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Kinto HIBI spoon 135mm

tds_purchase_m_kinto_27101
Read-onlyIdempotent

Recorded model HIBI spoon 135mm. 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_27101"
  }
}

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 openWorldHint=false, so the safety profile is clear without the description. The description adds domain context about exact variants and required clearances, but it does not explain what the tool computes, returns, or how it handles insufficient space.

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 definition is brief and mostly front-loaded, with each sentence providing guidance about model matching or measurements. The opening 'Recorded model HIBI spoon 135mm' is slightly awkward and does not establish the operation, but there is little wasted wording overall.

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 tool with no output schema and no parameter descriptions, so the description should explain more about how the measurements are used and what result the caller receives. It does not state the outcome of the check, the units beyond the parameter names, or how the required clearances are interpreted.

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 carry the burden of explaining five required parameters. It only says to use the seller’s model field or exact variant name and to use measurements including required clearances; it does not distinguish shelfDepthCm, productDepthCm, useClearanceCm, or frontClearanceCm in any meaningful way.

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 Kinto HIBI spoon, but the description itself only says 'Recorded model HIBI spoon 135mm' and gives input guidance. It identifies the product variant clearly but never states the actual operation, such as checking fit, evaluating clearances, or returning a result.

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 tells the caller to use the seller’s model field or exact variant name and to use measurements for the exact variant, which is input guidance rather than call-selection guidance. It does not say when to use this product-specific tool instead of a sibling such as tds_quote_storage_space or another product variant.

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.