Skip to main content
Glama

The Doll Scout Home Tools

Plan working clearance · Poppin Desk Organizer

tds_purchase_m_poppin_desk_organizer_105927
Read-onlyIdempotent

Recorded model Desk 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_desk_organizer_105927"
  }
}

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 establish read-only, idempotent, non-destructive behavior, so the description only needs to add computation context. Instead it adds very little: it hints that measurements must match the exact variant and include required clearances, but does not explain what the tool calculates, what output to expect, or how errors are handled.

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 wastes few words, but the opening sentence is uninformative and the purpose is not front-loaded. The guidance is compact but not structured around what an agent needs to decide or act.

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-parameter computation tool with no output schema and no parameter descriptions, the definition is materially incomplete. It omits the actual computation, units, constraints, and expected outcome, leaving the agent to infer how widths and margins interact.

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. The description provides only general guidance—use the seller model field or exact variant name, and use measurements for the exact variant including required clearances—without mapping meaning to each parameter (e.g., desktopWidthCm vs productWidthCm vs left/rightMarginCm) or explaining units beyond the cm suffix.

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 Desk Organizer,' which restates the product rather than stating what the tool does. It never says that the tool computes or checks working clearance; the only hint of purpose is in the title, not the description itself.

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 description gives input guidance ('Use the seller’s model field or exact variant name') but no when-to-use or when-not-to-use context. It does not mention alternatives among the many sibling purchase and planning tools.

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.