Skip to main content
Glama

The Doll Scout Home Tools

Check bathroom mounting clearance · Umbra Junip Tumbler

tds_purchase_m_umbra_junip_tumbler
Read-onlyIdempotent

Recorded model Junip Tumbler. 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>",
      "availableWidthCm": "<availableWidthCm>",
      "availableHeightCm": "<availableHeightCm>",
      "mountedWidthCm": "<mountedWidthCm>",
      "mountedHeightCm": "<mountedHeightCm>",
      "serviceMarginCm": "<serviceMarginCm>"
    },
    "name": "tds_purchase_m_umbra_junip_tumbler"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
mountedWidthCmYes
mountedHeightCmYes
serviceMarginCmYes
availableWidthCmYes
availableHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds only the notion of using measurements for the exact variant and "required clearances," without explaining what the check computes, what a failure means, or what the response looks like.

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?

The text is short and front-loaded, so it is not bloated. However, the first sentence duplicates the title, and the remaining sentences are under-specified rather than efficient, so the brevity comes at the cost of useful content.

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?

With six required numeric parameters, zero schema coverage, and no output schema, an agent needs the description to define each measurement and the clearance logic. It provides neither, so an agent cannot reliably construct the inputs or interpret the result.

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 carries the full burden. It only clarifies offeredModel (seller's model field or exact variant name) and vaguely alludes to "required clearances," leaving availableWidthCm, availableHeightCm, mountedWidthCm, mountedHeightCm, and serviceMarginCm entirely undefined in both schema and prose.

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?

The description opens with "Recorded model Junip Tumbler," which merely restates the title/name rather than stating what the tool does. It never says the tool checks whether the tumbler fits the available bathroom space given mounting dimensions and a service margin, so the actual verb and outcome must be inferred from the title alone.

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" is input guidance for one parameter, not when-to-use guidance. Nothing indicates when this clearance check applies versus any sibling tool, and no alternatives or preconditions are named.

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.