Skip to main content
Glama

The Doll Scout Home Tools

Plan display space · Umbra Ali Cat Ring Holder

tds_purchase_m_umbra_ali_cat_ring_holder
Read-onlyIdempotent

Recorded model Ali Cat Ring Holder. Use the seller’s model field or exact variant name. Use one upright layer of rectangular footprints. Check weight, height and stability separately.

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>",
      "usableWidthCm": "<usableWidthCm>",
      "usableDepthCm": "<usableDepthCm>",
      "footprintWidthCm": "<footprintWidthCm>",
      "footprintDepthCm": "<footprintDepthCm>",
      "gapCm": "<gapCm>"
    },
    "name": "tds_purchase_m_umbra_ali_cat_ring_holder"
  }
}

Input Schema

NameRequiredDescriptionDefault
gapCmYes
offeredModelYes
usableDepthCmYes
usableWidthCmYes
footprintDepthCmYes
footprintWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is low. The description does add scope context beyond them — single upright layer, rectangular footprints only, and that weight/height/stability are excluded — but it never says what the call produces or how the record is used downstream.

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 modeling constraint front-loaded. The telegraphic phrasing ("Recorded model…") costs some clarity, but nothing is padded.

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 six-parameter, all-required geometry tool with zero schema descriptions and no output schema, the description leaves half the inputs and all of the output semantics unexplained. What it does say is useful scope framing, but it is not sufficient for an agent to fill the schema 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% across six required parameters, so the description must compensate. It only gestures at offeredModel ("seller's model field") and the two footprint dimensions ("rectangular footprints"); usableWidthCm, usableDepthCm, and gapCm receive no explanation at all, and the relationship between usable area, footprint, and gap is undefined.

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?

"Recorded model Ali Cat Ring Holder" identifies the product but never states the action — the description is passive and the verb only appears in the title ("Plan display space"). An agent can infer this records a model's footprint for display planning, but it is not stated as verb + resource in the description itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/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" and "use one upright layer of rectangular footprints" give real invocation guidance for modeling, and "check weight, height and stability separately" implicitly scopes out work that belongs elsewhere. However, no sibling alternative is named and no condition for choosing among the many ring-holder models is offered.

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.