Skip to main content
Glama

The Doll Scout Home Tools

Plan display space · Umbra Infinity Picture Frame

tds_purchase_m_umbra_infinity_photo_frame
Read-onlyIdempotent

Recorded model Infinity 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_infinity_photo_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
gapCmYes
offeredModelYes
usableDepthCmYes
usableWidthCmYes
footprintDepthCmYes
footprintWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add one genuinely useful scope statement: weight, height and stability must be checked separately, so the agent knows this call covers geometry only. It says nothing about validation failures, units, or what the response contains.

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 filler, which is good, but the brevity is achieved by omitting the core action rather than by tight editing. The opening line is wasted on a restatement of the title, and the remaining rules are terse to the point of ambiguity.

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?

With six all-required numeric/string parameters, no schema descriptions, and no output schema, the definition needs to explain inputs and the computation. Instead it leaves the return value and three parameters undocumented and never clarifies units or geometry assumptions. An agent could not reliably construct a correct call from this text alone.

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 burden and largely fails. It clarifies offeredModel (seller's model field or exact variant name) and implies the two footprint parameters come in pairs for a single upright layer, but usableWidthCm, usableDepthCm and gapCm get no explanation at all, leaving three numeric inputs with only min/max bounds.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Recorded model Infinity Picture Frame', which restates the title rather than stating an action. It never says the tool plans or computes a display space; the only verb-like content ('Use one upright layer of rectangular footprints') is a constraint, not a purpose. An agent cannot tell from this text what the call actually produces.

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' gives guidance on how to fill one parameter, not when to choose this tool. There is no reference to alternatives such as the other Umbra frames or the quote/space-planning siblings, and no stated preconditions. The closest thing to scope guidance is 'Check weight, height and stability separately', which only says what this tool is not for.

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.