Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Kinto LIN plate 260mm

tds_purchase_m_kinto_20543
Read-onlyIdempotent

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

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?

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world check. The description adds that the exact variant and measurements including clearances are required, but it does not explain what the tool computes, what a fit result means, or how failures are reported.

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?

The description is short and not padded, but it is poorly front-loaded: the first sentence restates the product rather than stating the check being performed. The remaining sentences are compact input instructions, but the structure delays the useful information.

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 read-only fit-check tool with five required parameters, no parameter descriptions, and no output schema, the definition should explain both the measurement inputs and what the check returns. It gives only minimal input guidance and leaves the result behavior and parameter meanings largely undocumented.

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%, so the description must carry the burden for all five parameters. It clarifies offeredModel somewhat and refers generally to measurements and required clearances, but it does not distinguish shelfDepthCm, productDepthCm, useClearanceCm, and frontClearanceCm or specify units and measurement expectations.

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 only says 'Recorded model LIN plate 260mm' and then gives input advice; it never states the action, such as checking whether the plate fits a shelf or kitchen space. The title supplies the purpose, but the description itself largely restates the product rather than defining the tool's operation.

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 guidance on choosing the offeredModel value ('seller’s model field or exact variant name') but does not say when to use this tool, when not to use it, or how it relates to alternatives such as tds_quote_storage_space.

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.