Skip to main content
Glama

The Doll Scout Home Tools

Plan display space · Umbra Wishbone Picture Frame

tds_purchase_m_umbra_wishbone_desk_frame
Read-onlyIdempotent

Recorded model Wishbone 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_wishbone_desk_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
gapCmYes
offeredModelYes
usableDepthCmYes
usableWidthCmYes
footprintDepthCmYes
footprintWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not disclose what the tool produces (a stored record? a computed envelope?), what happens if the model is unknown, or how the 'one upright layer' constraint affects inputs that violate it. For a 6-required-parameter computation-like tool, this is thin.

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, no filler, reasonably front-loaded with the model identity. However, the terse style trades clarity for brevity: 'Recorded model Wishbone Picture Frame' is ambiguous, and the constraints are compressed into fragments that leave relationships unexplained.

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 no output schema, no annotations beyond a read-only profile, and 0% schema description coverage across six required parameters, the description should explain the geometry model (usable area, footprint, gap) and the relationship between them. It instead offers three brief imperatives, leaving an agent unable to compute valid values or know what the result represents.

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

Parameters1/5

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

Schema description coverage is 0% for six required numeric/string parameters, so the description must carry the meaning of usableWidthCm, usableDepthCm, footprintWidthCm, footprintDepthCm and gapCm. It supplies none: 'gapCm' is never explained (gap between what?), and it is unclear whether footprint dimensions must be ≤ usable dimensions. The single hint 'one upright layer of rectangular footprints' does not map to any specific parameter.

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 identifies the product (Umbra Wishbone Picture Frame) but the description's operative sentence is procedural: 'Use one upright layer of rectangular footprints.' It does not state a clear verb+resource like 'compute placement/envelope for this frame model'. The tool appears to record/plan a footprint configuration for a specific furniture model, but the agent must infer that purpose from the parameter names (usableWidthCm, footprintWidthCm, gapCm).

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?

It says to use the seller's model field or exact variant name, which is a parameter-input instruction rather than when-to-use guidance. There is no statement of when this tool should be chosen over siblings like tds_quote_framing_plan, tds_static_art_frame_height, or the other Umbra frame tools, and no exclusions. 'Check weight, height and stability separately' hints at scope boundaries but is too terse to route the agent.

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.