Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Kinto HIBI knife 215mm

tds_purchase_m_kinto_27107
Read-onlyIdempotent

Recorded model HIBI knife 215mm. 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_27107"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so no safety burden remains. Beyond that the description adds nothing behavioral: it does not say what the check returns, what happens if the variant name does not match, or how clearances are evaluated. It repeats the model name rather than disclosing behavior.

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?

Two short sentences with no padding, and the model identifier is front-loaded. The second sentence compresses two separate instructions ('seller's model field', 'exact variant name') without excessive wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple and read-only with no output schema, so the description need not explain return values. But with five required parameters at 0% schema coverage, an agent is left guessing how the four measurement fields relate and what the check actually evaluates, which is a real gap for a fit-checking tool.

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 numeric/string parameters, so the description must carry the burden. It hints that offeredModel should come from the seller's model field and that clearances must be included, but it never distinguishes shelfDepthCm from productDepthCm or useClearanceCm from frontClearanceCm, nor states units (cm is only implied by parameter names).

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 establishes the action (check kitchen space) and the product variant (Kinto HIBI knife 215mm), and the first sentence pins the exact recorded model, which distinguishes it from the many product-specific siblings. However, the description body never states the verb or outcome — that this tool verifies whether the product fits given the supplied measurements — so the agent must infer purpose from the title alone.

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 given ('Use the seller's model field or exact variant name', 'Use measurements for the exact variant') is about filling parameters, not about when to choose this tool over alternatives. The sibling tds_quote_storage_space is never mentioned, and there is no when-not guidance or statement of prerequisites.

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.