Skip to main content
Glama

The Doll Scout Home Tools

Plan display space · Umbra Tini Ring Holder

tds_purchase_m_umbra_tini_ring_holder
Read-onlyIdempotent

Recorded model Tini 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_tini_ring_holder"
  }
}

Input Schema

NameRequiredDescriptionDefault
gapCmYes
offeredModelYes
usableDepthCmYes
usableWidthCmYes
footprintDepthCmYes
footprintWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds domain behavior — that the model is cataloged and that layout uses a single upright layer of rectangular footprints — but says nothing about output format, units handling, or what happens when the requested space is too small.

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 front-loads the model identity, but the opening sentence "Recorded model Tini Ring Holder" is nearly tautological with the name and gives little information. The remaining sentences are dense but telegraphic rather than structured.

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 six required numeric parameters, no output schema, and zero schema descriptions, the definition leaves the agent guessing about units, how usable vs footprint dimensions interact, and what the tool returns. The constraints given are relevant but far short of what is needed to call it correctly.

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, and the description only loosely maps to two of them: the model field (offeredModel) and rectangular footprints (footprintWidthCm/footprintDepthCm). It never explains usableWidthCm vs footprintWidthCm, or what gapCm means (spacing between items?), leaving most parameters undocumented in both places.

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 title and the phrase "Recorded model Tini Ring Holder" identify the resource, and "Use one upright layer of rectangular footprints" hints that this plans a display footprint. However, the description never states a clear verb or what the tool actually produces (a layout plan, a stored record, a validation result), so the agent must infer its function.

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" is guidance about a parameter value, not about when to choose this tool over the many sibling ring-holder and display-plan tools. "Check weight, height and stability separately" gestures at other checks but names no alternative tool or condition.

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.