Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Kinto HIBI cutlery set

tds_purchase_m_kinto_27100
Read-onlyIdempotent

Recorded model HIBI cutlery set. 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_27100"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/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 covered. The description adds nothing further — it does not say what the call returns (presumably a fit/clearance verdict), whether values are validated, or how measurements are interpreted.

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?

Three short sentences with no filler and no repetition. It is compact, though it front-loads the product identity rather than the tool's action, which is the less useful lead.

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?

For a five-required-number fit-check with no output schema and no parameter descriptions, the description is too thin: it omits units, the meaning of each clearance figure, and what the result represents. An agent could supply plausible numbers but would be guessing at their semantics.

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 carries the full burden for five required parameters. It clarifies offeredModel (seller's model field or exact variant name) and gestures at 'measurements ... including required clearances', but never explains the difference between useClearanceCm and frontClearanceCm, nor confirms units despite the 'Cm' suffixes.

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 opens with 'Recorded model HIBI cutlery set', which mostly restates the title/product rather than stating what the tool computes. The mention of 'required clearances' hints at a fit/space check, but no verb such as 'check whether this cutlery set fits the shelf' is given, and nothing distinguishes it from tds_quote_storage_space.

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 guidance present ('Use the seller's model field or exact variant name', 'Use measurements for the exact variant') is about how to fill parameters, not when to call this tool versus alternatives. There is no statement of prerequisites, when-not-to-use, or relation to the sibling space-quoting tool.

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.