Skip to main content
Glama

The Doll Scout Home Tools

Plan display space · Umbra Flute Picture Frame

tds_purchase_m_umbra_flute_picture_frame
Read-onlyIdempotent

Recorded model Flute 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_flute_picture_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 declare a safe, idempotent, closed-world read, so the description's marginal value is its modeling assumption (a single upright layer of rectangular footprints) and its scope boundary (weight, height and stability are out of scope). That is genuine added context, but it omits what the result actually is and any preconditions on the supplied measurements.

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?

Four short sentences with no bloat, but the lead sentence ('Recorded model Flute Picture Frame') earns nothing beyond the title, and the actionable constraints are buried mid-paragraph rather than front-loaded.

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?

A fully required six-parameter planning tool with zero schema descriptions, no output schema and no explanation of the returned plan. The description should define the geometric model (units, whether gapCm is spacing between frames or to the wall) and the output; it covers only a fraction of that.

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 carry the load. It only clarifies offeredModel (seller's model field or exact variant name) and vaguely gestures at footprint and gap via 'rectangular footprints'; usableWidthCm, usableDepthCm and especially gapCm (gap between what?) remain undefined in both schema and description.

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') but the description itself opens with 'Recorded model Flute Picture Frame', which restates the product name rather than stating the action. The phrase 'Use one upright layer of rectangular footprints' hints at a footprint/layout computation, yet an agent still cannot say precisely what the tool produces (a plan? a validation? a recorded measurement).

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?

Two directives are present: use the seller's model field or exact variant name when calling, and check weight, height and stability separately. The second implicitly excludes those checks from this tool but never names a specific sibling to use instead, so guidance is implied rather than explicit.

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.