Skip to main content
Glama

The Doll Scout Home Tools

Plan display space · Umbra Luna Wall Multi-Picture Frame

tds_purchase_m_umbra_luna_photo_frame
Read-onlyIdempotent

Recorded model Luna Wall Multi-Picture 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_photo_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
gapCmYes
offeredModelYes
usableDepthCmYes
usableWidthCmYes
footprintDepthCmYes
footprintWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already establish a read-only, idempotent, non-destructive, closed-world operation, so safety is covered. The description adds useful scope boundaries (one upright layer; weight/height/stability checked separately), but it does not explain output, errors, or how dimensions are interpreted.

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 each sentence carries some instruction, but it opens with a model-name fragment rather than a clear purpose statement. It is concise but not well structured for an agent scanning for action and parameter meaning.

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 parameters, no schema descriptions, and no output schema, the description is far too thin. It leaves the agent unable to determine what is returned or how most dimensions and the gap parameter affect the plan.

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% for six required parameters. The description only maps offeredModel to the seller's model field or exact variant and vaguely links footprint dimensions to 'one upright layer'; it never explains gapCm, usableWidthCm, usableDepthCm, or units. Partial compensation only.

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 description identifies the exact product ('Luna Wall Multi-Picture Frame') and gives footprint/check constraints, but it never states the action the tool performs (e.g., calculate fit, record a model, or plan display space). The title supplies 'Plan display space', yet the description itself leaves the operation vague and does not distinguish it from sibling frame tools.

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?

It offers procedural constraints—use the seller's model field or exact variant, use one upright layer of rectangular footprints, and check weight/height/stability separately—which implies the tool handles footprint planning only. However, it does not say when to choose this tool over tds_quote_framing_plan or other frame tools, nor does it name exclusions.

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.