Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · Umbra Bird Cafe

tds_purchase_m_umbra_bird_cafe
Read-onlyIdempotent

Recorded model Bird Cafe. Use the seller’s model field or exact variant name. Use measurements for the exact variant, including required clearances.

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>",
      "itemWidthCm": "<itemWidthCm>",
      "itemDepthCm": "<itemDepthCm>",
      "itemHeightCm": "<itemHeightCm>",
      "innerWidthCm": "<innerWidthCm>",
      "innerDepthCm": "<innerDepthCm>",
      "innerHeightCm": "<innerHeightCm>",
      "paddingCm": "<paddingCm>"
    },
    "name": "tds_purchase_m_umbra_bird_cafe"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add context. It contributes the constraint that measurements must be for the exact variant and must include required clearances, which is genuinely useful precision guidance, but it never says what the tool returns (boolean, pass/fail, recommended dimensions) or whether padding is added per side.

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 filler, but the structure is backwards: the most informative sentence (exact variant plus clearances) trails, and the lead sentence is a near-restatement of the title that conveys no actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is an 8-required-parameter computation tool with no output schema and no annotation-derived output info. The description omits both the units/direction of the dimension pairs and the shape of the fit result, which is the single thing the agent most needs to interpret the response.

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?

With 8 required parameters at 0% schema description coverage, the description must carry the semantics and mostly does not. It clarifies offeredModel (seller's model field or exact variant name) and gestures at the measurement/clearance parameters, but leaves the item-vs-inner dimension pairs and the meaning of paddingCm (per-side versus total, in cm) completely undefined.

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 never states the core action; the verb "check storage fit" only appears in the title, while the body opens with the opaque fragment "Recorded model Bird Cafe." An agent can infer this validates an item against a container, but the description itself does not say it computes a fit verdict, and the "tds_purchase_" name prefix points in a different direction.

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" tells the agent how to fill one parameter, not when this tool applies versus siblings like tds_quote_storage_space or tds_landed_storage_cart. There is no when-not guidance and no stated prerequisite that the item and container dimensions must come from the same variant.

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.