Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Kinto HIBI spoon 185mm

tds_purchase_m_kinto_27103
Read-onlyIdempotent

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

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds that matching must be done against the exact variant and its required clearances, which is useful behavioral context, but it says nothing about what the check returns, what happens when clearances are insufficient, or any units/threshold assumptions.

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 little waste, and the identification comes first. However, the first sentence merely repeats the title's product name, and the remaining text is cryptic enough that brevity comes at the cost of understanding.

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-parameter tool with zero schema descriptions and no output schema, the definition should explain what the verdict means and how each measurement is interpreted. It leaves the agent guessing about the computation and return shape, which is inadequate for this complexity.

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% with five required parameters, so the description carries the full burden. It only loosely maps to them: 'seller's model field or exact variant name' covers offeredModel, and 'measurements ... including required clearances' gestures at the four numeric fields without distinguishing shelf depth from product depth, use clearance, or front clearance, nor confirming the centimetre units.

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 identifies the product ('Recorded model HIBI spoon 185mm') but never states the operation — nothing says it checks whether the spoon fits a shelf, what it returns, or how it differs from the many sibling tds_purchase_m_* tools. The verb lives only in the title ('Check kitchen space'), so the description itself is close to a restatement of the name/title.

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-level guidance ('use the seller's model field or exact variant name', 'use measurements for the exact variant'), which hints at how to supply data, but there is no when-to-use context, no exclusions, and no routing to alternatives such as tds_quote_storage_space. An agent cannot tell from this text when this tool is the right choice.

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.