Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Poppin Drawer Organizer

tds_purchase_m_poppin_drawer_organizer_105928
Read-onlyIdempotent

Recorded model Drawer Organizer. 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_drawer_organizer_105928"
  }
}

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?

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond annotations: it does not explain what is computed, what the response represents, or how clearance values are evaluated.

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 description is short and contains no obvious filler beyond the opening fragment 'Recorded model Drawer Organizer,' which is awkward and not front-loaded as a clear statement of purpose. The remaining sentences are efficient but read as parameter notes rather than a structured explanation of the tool.

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 read-only planning tool with five required numeric parameters, no output schema, and no schema parameter descriptions, the definition is incomplete. It does not explain the clearance calculation, the meaning of the margin parameters, or what the agent should expect to receive, leaving too much inferable only from the title.

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 across five required parameters, the description must carry parameter meaning. It partially explains offeredModel (seller's model field or exact variant name) and alludes to measurements and required clearances, but it leaves desktopWidthCm, productWidthCm, leftMarginCm, and rightMarginCm without individual meaning or units.

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 names the resource (Drawer Organizer) and hints at using measurements and clearances, but it never states a clear verb such as compute, check fit, or plan clearance. The title supplies the missing action, so an agent can infer the purpose, but the description alone is vague rather than explicit about what the tool produces.

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 about parameter sourcing: use the seller's model field or exact variant name, and use measurements for the exact variant. It does not say when to choose this tool over related planning or purchase tools, nor does it mention any exclusions or prerequisites.

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.