Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Kinto LIN plate 230mm

tds_purchase_m_kinto_20542
Read-onlyIdempotent

Recorded model LIN plate 230mm. 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_20542"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds one useful behavioral note: clearances must be included for the exact variant, implying this is a fit/clearance computation where variant accuracy matters. It does not say what the result consists of (pass/fail, margin, warnings), and there is no output schema to fill that gap.

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 the variant-matching constraint is front-loaded. It is lean to the point of under-specification, but nothing is redundant.

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?

For a read-only single-product fit check with five required numeric/string inputs and no output schema, the definition should at minimum say what is being compared and what a result means. It hints at clearance checking but leaves the semantics of four measurement fields, their units, and the return value unexplained.

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 parameters, so the description must carry the load. It explains offeredModel ('seller's model field or exact variant name') and gestures at the four measurement parameters ('measurements ... including required clearances'), but never distinguishes shelfDepthCm from productDepthCm or useClearanceCm from frontClearanceCm, nor states units or how values are compared.

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 LIN plate 230mm', which mostly restates the title and the product identity rather than naming an action. Combined with the title 'Check kitchen space', an agent can infer this validates a product's fit against shelf/front clearances, but the description itself never states that verb or outcome.

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?

'Use the seller's model field or exact variant name' gives input-sourcing advice, not tool-selection advice. Nothing says when this check is required versus the sibling tds_quote_storage_space, nor what to do if the fit fails.

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.