Skip to main content
Glama

The Doll Scout Home Tools

Plan display space · VASAGLE Plattenspieler-Ständer

tds_purchase_m_vasagle_vasagle_plattenspieler_staen_b8e18125
Read-onlyIdempotent

Recorded model Plattenspieler-Ständer. Use the seller’s model field or exact variant name. Use one upright layer of rectangular footprints. Check weight, height and stability separately.

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>",
      "usableWidthCm": "<usableWidthCm>",
      "usableDepthCm": "<usableDepthCm>",
      "footprintWidthCm": "<footprintWidthCm>",
      "footprintDepthCm": "<footprintDepthCm>",
      "gapCm": "<gapCm>"
    },
    "name": "tds_purchase_m_vasagle_vasagle_plattenspieler_staen_b8e18125"
  }
}

Input Schema

NameRequiredDescriptionDefault
gapCmYes
offeredModelYes
usableDepthCmYes
usableWidthCmYes
footprintDepthCmYes
footprintWidthCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world operation, so the safety profile is covered. The description adds genuinely useful scope limits: only one upright layer, only rectangular footprints, and weight/height/stability are out of scope. It still says nothing about what is returned or how the fit is judged, so the added value is moderate rather than rich.

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?

Four short imperative sentences with no filler and the key constraints front-loaded. The opening sentence ('Recorded model Plattenspieler-Ständer') is largely redundant with the title, which is the only wasted line.

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?

Six required parameters, zero schema descriptions, no output schema, and a mutation-free planning tool whose result format is unstated. With nothing explaining gapCm or the usable-dimension semantics and no indication of what the tool produces, an agent cannot reliably construct a correct call from this definition alone.

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%, so the description must carry parameter meaning. It maps 'seller's model field or exact variant name' to offeredModel and 'rectangular footprints' to footprintWidthCm/footprintDepthCm, but usableWidthCm, usableDepthCm and especially gapCm are never explained, leaving half the required parameters undefined anywhere.

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 title says 'Plan display space' for a VASAGLE record-player stand, but the description itself opens with 'Recorded model Plattenspieler-Ständer,' which restates the tool name rather than stating what the tool computes. The remaining sentences are instructions rather than a purpose statement, so an agent must infer that this plans a rectangular footprint layout for one recorded model. Nothing distinguishes it from the many sibling tds_purchase_m_* model tools beyond the model 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?

'Use the seller's model field or exact variant name' and 'Use one upright layer of rectangular footprints' give concrete usage constraints, and 'Check weight, height and stability separately' tells the agent this tool does not cover those checks. However, there is no explicit when-to-use/when-not versus alternatives such as tds_preflight_display_stands or tds_display_riser_load, so routing must be guessed from the model name.

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.