Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Kinto HIBI fork 140mm

tds_purchase_m_kinto_27104
Read-onlyIdempotent

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

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 fully covered. Beyond that, the description adds only the vague hint that clearances are 'required', without saying what the tool returns, whether a failed clearance produces an error or a verdict, or how the shelf/product/clearance numbers are compared.

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 padding, and the actionable instructions come before the trailing clearance note. The opening sentence, however, is a low-value restatement of the product name rather than a purpose statement.

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-required-parameter, zero-coverage, no-output-schema tool needs the description to explain units, how clearances are applied, and what the result means. The definition supplies none of this, so an agent knows which fields to fill but not how the evaluation works or what it will receive back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and all five parameters are required, so the description has to compensate. It does clarify that offeredModel should carry the seller's model string or exact variant name, but it lumps shelfDepthCm, productDepthCm, useClearanceCm and frontClearanceCm under a single 'measurements ... including required clearances' phrase, leaving the distinction between product depth, use clearance and front clearance undocumented.

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 opens with the fragment 'Recorded model HIBI fork 140mm', which identifies the product but never states a verb or what the tool actually does. Only the title ('Check kitchen space') conveys that this evaluates fit, and that meaning is not repeated or elaborated in the description body.

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 text gives input-sourcing instructions ('Use the seller's model field or exact variant name') but no guidance on when to call this tool, when not to, or how it relates to siblings like tds_quote_storage_space. An agent must infer the use case entirely from the title.

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.