Skip to main content
Glama

The Doll Scout Home Tools

Plan display space · Umbra Flute Wall Picture Frames, Set of 4

tds_purchase_m_umbra_flute_gallery_pd
Read-onlyIdempotent

Recorded model Flute Wall Picture Frames, Set of 4. 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_flute_gallery_pd"
  }
}

Input Schema

NameRequiredDescriptionDefault
gapCmYes
offeredModelYes
usableDepthCmYes
usableWidthCmYes
footprintDepthCmYes
footprintWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds a useful caveat that weight, height, and stability must be checked separately and that layout assumes a single upright layer, but it does not explain return behavior or operational limits.

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. However, the opening 'Recorded model...' is an awkward front-load; the action would be clearer if stated first.

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-required-parameter planning tool with no output schema and no parameter descriptions, the definition is incomplete: it omits dimension/gap semantics and return behavior, leaving most required inputs unexplained.

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 clarifies offeredModel ('seller's model field or exact variant name') and the footprint concept, but does not define usableWidthCm, usableDepthCm, footprintWidthCm, footprintDepthCm, or gapCm.

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?

Identifies the product ('Flute Wall Picture Frames, Set of 4') and implies layout planning via 'one upright layer of rectangular footprints,' but never states the actual operation (e.g., calculate/plan display layout) or distinguishes it from nearby Umbra 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Only says to use the seller's model or exact variant name and one upright footprint layer; there is no explicit when-to-use guidance, prerequisites, or comparison to alternatives such as tds_quote_framing_plan or other 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.