Skip to main content
Glama

The Doll Scout Home Tools

Plan display space · Umbra Luna Gallery Frame

tds_purchase_m_umbra_luna_gallery_frame
Read-onlyIdempotent

Recorded model Luna Gallery Frame. 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_luna_gallery_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
gapCmYes
offeredModelYes
usableDepthCmYes
usableWidthCmYes
footprintDepthCmYes
footprintWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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 the safety profile is covered. The description adds real scope boundaries beyond that: it only models a single upright layer of rectangular footprints and explicitly defers weight, height and stability to separate checks. It does not disclose units, output shape, or what happens with the gap value, so the added context is meaningful but partial.

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?

Three short sentences with no filler, but they are telegraphic fragments ("Recorded model Luna Gallery Frame") rather than a front-loaded statement of purpose. The ordering puts terse data constraints before any explanation of function, which is efficient but reads awkwardly.

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?

Six required parameters with zero schema descriptions and no output schema demand more than these fragments provide. The description never explains how usableWidth/usableDepth relate to footprintWidth/footprintDepth, what gapCm controls, or what the tool returns, leaving the agent to infer the core geometry model of a planning tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, the description carries the full burden, and the parameter names are already largely self-describing; the description adds real meaning for offeredModel by requiring the seller's model field or exact variant name. It does not clarify the distinction between usable and footprint dimensions or how gapCm is applied, but the naming plus that one clarification keeps it above the minimum baseline.

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 supplies the verb ("Plan display space") for a specific model, and the description pins the subject down as "Recorded model Luna Gallery Frame" with rectangular footprints in one upright layer. However, the description itself never states what the tool computes or produces, relying on fragments rather than a clear verb+resource statement, and does not differentiate itself from sibling product-specific tools beyond the model name.

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" gives concrete input-sourcing guidance, and "Check weight, height and stability separately" implicitly scopes out checks handled elsewhere. What is missing is explicit routing – no sibling tools are named for the weight/height/stability checks, and there is no statement of when this tool should be preferred over the other Umbra frame tools.

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.