Skip to main content
Glama

The Doll Scout Home Tools

Plan display space · Umbra Exhibit Wall Picture Frames, Set of 9

tds_purchase_m_umbra_exhibit_9op
Read-onlyIdempotent

Recorded model Exhibit Wall Picture Frames, Set of 9. 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_exhibit_9op"
  }
}

Input Schema

NameRequiredDescriptionDefault
gapCmYes
offeredModelYes
usableDepthCmYes
usableWidthCmYes
footprintDepthCmYes
footprintWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered. The description adds that the representation is a single upright layer of rectangular footprints and that weight/height/stability are handled elsewhere, but it says nothing about what is created, whether it persists, or what is returned.

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, front-loaded sentences with no filler, and the operational constraints follow immediately after the product identification. The phrasing is terse to the point of being cryptic rather than padded, so brevity is not the problem.

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 spatial modeling tool with no output schema and no parameter descriptions, the definition leaves the core distinction between usable width/depth, footprint width/depth and the gap unexplained. An agent could not reliably compute or interpret most of the numeric inputs 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 semantic load and largely does not. It clarifies only offeredModel (seller's model field or exact variant name) and vaguely gestures at footprintWidthCm/footprintDepthCm via "rectangular footprints"; usableWidthCm, usableDepthCm and gapCm receive no explanation at all.

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 pairs a product name ("Exhibit Wall Picture Frames, Set of 9") with partial modeling direction ("one upright layer of rectangular footprints"), so an agent can infer this registers a product footprint into a display-space plan. However, the opening "Recorded model" is not a clear verb+resource statement, and nothing distinguishes its role from plan-oriented siblings such as tds_quote_exhibit_display.

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 gives corrective usage hints: "Use the seller's model field or exact variant name" and "Check weight, height and stability separately," which tell the agent the identity must be exact and that other checks are out of scope. It never states when to choose this tool versus an alternative or what prerequisites exist, so selection guidance remains implicit.

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.