Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Kikkerland Clip-on Light

tds_purchase_m_kikkerland_clip_on_light
Read-onlyIdempotent

Recorded model Clip-on Light. 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>",
      "desktopWidthCm": "<desktopWidthCm>",
      "productWidthCm": "<productWidthCm>",
      "leftMarginCm": "<leftMarginCm>",
      "rightMarginCm": "<rightMarginCm>"
    },
    "name": "tds_purchase_m_kikkerland_clip_on_light"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftMarginCmYes
offeredModelYes
rightMarginCmYes
desktopWidthCmYes
productWidthCmYes

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, destructiveHint=false and a closed-world catalog, so the safety profile is covered. The description adds nothing beyond that: it does not say whether the tool validates that the clearance fits, what it returns, or whether offeredModel must match a catalog entry exactly. "Recorded model" gestures at a known catalog but never clarifies behavior on a miss.

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?

Two short sentences with no filler, so it is efficiently sized. However it is not front-loaded with purpose and the opening sentence is wasted on a name restatement, so brevity here comes at the cost of clarity rather than from it.

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?

With five required numeric parameters, zero schema descriptions and no output schema, the description should explain what each measurement represents and what the call produces. It does neither, so an agent knows it must supply numbers but not how they are interpreted or what comes back.

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 only explains offeredModel (seller's model field or exact variant name) and vaguely gestures at "measurements... including required clearances" for the four numeric fields, leaving desktopWidthCm, productWidthCm and the two margin parameters without any stated meaning, unit or relationship.

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 Clip-on Light" largely restates the title and never names the action the tool performs (recording? validating? planning clearance?). The only functional signal is "Use measurements for the exact variant, including required clearances," which hints at clearance planning but never says so directly, so an agent cannot confidently distinguish this from the many other purchase-family siblings.

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 description gives input-selection advice ("use the seller's model field or exact variant name"), which is parameter guidance rather than when-to-use guidance. It never states preconditions, what to do if the variant is unknown, or any alternative tool to call instead.

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.