Skip to main content
Glama

The Doll Scout Home Tools

Plan display space · NIUBEE Graduated Acrylic Risers — Two Sets

tds_purchase_niubee_risers
Read-onlyIdempotent

Recorded model 3-, 4- and 5-inch riser set. 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_niubee_risers"
  }
}

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 the safety profile is covered. The description adds useful behavioral scope by telling the agent this covers one upright layer only and that weight/height/stability are handled elsewhere. It does not say what the tool produces or whether usable dimensions are consumed versus validated.

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?

Four short sentences with no filler, and the product/variant identification is front-loaded. The phrasing is terse to the point of being cryptic ("one upright layer of rectangular footprints"), but nothing is redundant.

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 tool with zero schema coverage and no output schema, the description leaves major gaps: gapCm is unexplained, the relationship between usableWidthCm/usableDepthCm and footprint dimensions is unstated, and the tool's result or computed quantity is never described. It covers the model field and one modeling constraint, which is far short of what this parameter surface requires.

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 adds real meaning for offeredModel (seller's model field or exact variant name) and hints that footprintWidth/DepthCm describe rectangles. It says nothing about gapCm, the usable-vs-footprint distinction, or units for the cm-suffixed fields.

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?

"Recorded model 3-, 4- and 5-inch riser set" identifies the exact product and variant scope, which helps distinguish it from the other purchase_* siblings. However, the description never states the verb or outcome — it never says whether the tool records a purchase, computes riser layout capacity, or validates dimensions. An agent knows the subject matter but not the action.

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" and "Use one upright layer of rectangular footprints" are genuine input-usage constraints. "Check weight, height and stability separately" implies out-of-scope checks but never names a sibling tool or states when to prefer this over, say, tds_unit_price_stack_risers or tds_display_riser_load.

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.