Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Poppin Key Desk, 48"

tds_purchase_m_poppin_key_desk_48_108124
Read-onlyIdempotent

Recorded model Key Desk, 48". 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_key_desk_48_108124"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftMarginCmYes
offeredModelYes
rightMarginCmYes
desktopWidthCmYes
productWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds no further behavioral context such as what is returned, whether values are stored, or how invalid measurements are handled; it only repeats input constraints.

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?

The description is very short and front-loads the variant name, with no wasted sentences. However, the opening fragment “Recorded model Key Desk, 48”.” is awkward and the measurement guidance is broad rather than structured.

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 tool with no schema descriptions and no output schema, the definition leaves units, margin meaning, return behavior, and error handling unspecified. It is not complete enough for reliable 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?

With 0% schema description coverage, five required parameters remain mostly undefined. The description touches offeredModel and vaguely says measurements include clearances, but leftMarginCm, rightMarginCm, desktopWidthCm, and productWidthCm have no units or meaning explained.

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 names the product variant but never states the action: it does not say whether the tool records, purchases, plans clearance, or computes fit. Without the title, an agent could not infer the operation, and there is no sibling differentiation beyond the product name.

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?

It gives input guidance by saying to use the seller’s model field or exact variant name and to use measurements for the exact variant, including required clearances. This implies the tool is for this product’s clearance planning, but it does not provide explicit when-to-use or when-not-to-use guidance versus alternatives.

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.