Skip to main content
Glama

The Doll Scout Home Tools

Plan display space · Umbra Gracie Ring Holder

tds_purchase_m_umbra_gracie_ring_holder
Read-onlyIdempotent

Recorded model Gracie Ring Holder. 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_gracie_ring_holder"
  }
}

Input Schema

NameRequiredDescriptionDefault
gapCmYes
offeredModelYes
usableDepthCmYes
usableWidthCmYes
footprintDepthCmYes
footprintWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real scope information by stating the layout is a single upright layer of rectangular footprints and that weight, height, and stability are evaluated separately, telling the agent this tool does not perform those checks. It does not disclose what the result contains or how gaps are applied.

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?

Three short sentences with no padding, and the layout rule is reasonably front-loaded after the model identifier. However, the opening fragment spends a sentence conveying almost no information, and the parameter hints are interleaved rather than grouped.

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 six-required-parameter calculation tool with no output schema and zero schema coverage needs the description to define each measurement's meaning and units. The definition instead leaves the usable-vs-footprint semantics and the gap parameter entirely undocumented, which is a material gap for correct invocation.

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 numeric parameters, so the description carries the full burden and mostly fails. It clarifies only the model identifier; it never explains the crucial distinction between usableWidthCm/usableDepthCm (available space) and footprintWidthCm/footprintDepthCm (item size), nor what gapCm measures.

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?

"Recorded model Gracie Ring Holder" is a fragment that restates the product name rather than stating what the tool computes. The layout instruction ("one upright layer of rectangular footprints") hints at a footprint-packing calculation, but the agent must infer the actual operation from the title and tool name rather than from the description.

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?

"Use the seller's model field or exact variant name" gives concrete guidance on how to populate the model argument, which is genuinely useful. "Check weight, height and stability separately" implies those concerns are handled elsewhere, but no sibling tool is named and there is no explicit when-not guidance.

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.