Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Poppin Nomad Task Chair

tds_purchase_m_poppin_nomad_task_chair_107930
Read-onlyIdempotent

Recorded model Nomad Task Chair. 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>",
      "desktopWidthCm": "<desktopWidthCm>",
      "productWidthCm": "<productWidthCm>",
      "leftMarginCm": "<leftMarginCm>",
      "rightMarginCm": "<rightMarginCm>"
    },
    "name": "tds_purchase_m_poppin_nomad_task_chair_107930"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftMarginCmYes
offeredModelYes
rightMarginCmYes
desktopWidthCmYes
productWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so safety is covered. The description adds nothing about the outcome — no indication of whether it returns a clearance verdict, a computed margin, or an echo of inputs — which matters because there is no output schema.

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 little padding, but the first is a dangling fragment and the actual purpose is never front-loaded. Brevity here comes partly from omission rather than efficient phrasing.

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 five-required-parameter computational tool with no output schema and no parameter descriptions, the definition omits what is computed and what is returned. What remains is only a weak hint about valid model naming and measurement sourcing.

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 five required parameters, so the description carries the full burden. It hints that offeredModel should be a seller model field or exact variant name and that numeric inputs are measurements for the exact variant, but it never explains the distinction between leftMarginCm and rightMarginCm, the relationship of desktopWidthCm to productWidthCm, or expected units.

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 title says 'Plan working clearance' but the description never states a verb for the tool itself; 'Recorded model Nomad Task Chair' is a fragment rather than an action statement. An agent cannot confidently tell whether this records a model, computes clearance, or validates measurements against clearance requirements, nor how it differs from the many sibling Poppin product tools.

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?

The only guidance is input-level ('Use the seller's model field or exact variant name'), which is about which value to pass rather than when to call this tool. There is no statement of prerequisites, when-not-to-use, or how it relates to sibling chair and desk tools, leaving the agent to infer the scenario.

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.