Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Kinto LIN plate 170mm

tds_purchase_m_kinto_20541
Read-onlyIdempotent

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

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds no behavior beyond that: it does not say what the tool returns (a fit verdict?), whether clearances are evaluated against shelf depth, or what happens when a fit fails, and there is no output schema to backfill this.

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?

Only three short sentences with no bloat, but the lead sentence is a wasted restatement of the product name, so the useful content (which values to supply) is not front-loaded. Restructuring to lead with the action would earn more.

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 tool with five required numeric parameters, zero schema documentation and no output schema, the definition is far too thin. An agent would have to guess units, the meaning of each depth/clearance value, and what the response looks like before it could call this confidently.

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% for 5 required parameters, so the description carries the full burden. It clarifies offeredModel (seller's model field or exact variant name) and vaguely gestures at the measurements and clearances, but never distinguishes shelfDepthCm from productDepthCm, nor useClearanceCm from frontClearanceCm, nor states units or how they are combined.

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?

"Recorded model LIN plate 170mm" restates the product identity from the title rather than stating an action; there is no verb describing what the tool actually does (validate fit? record a purchase?). An agent cannot tell from the description alone how this differs from the per-SKU siblings such as tds_purchase_m_kinto_20542 or 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 given ("Use the seller's model field or exact variant name") is about which value to supply, not about when this tool should be called instead of the many sibling product tools. No prerequisites, no conditions for choosing this SKU tool over another, and no statement of what problem it solves.

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.