Skip to main content
Glama

The Doll Scout Home Tools

Calculate row spacing · Trading card display stands

tds_trading_card_stand_row
Read-onlyIdempotent

Compute usable row width, whole-item capacity and remaining clearance from measurements. Trading card display stands. End reserve for price labels (mm).

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": {
      "insideWidthMm": "<insideWidthMm>",
      "itemWidthMm": "<itemWidthMm>",
      "itemGapMm": "<itemGapMm>",
      "labelEndReserveMm": "<labelEndReserveMm>"
    },
    "name": "tds_trading_card_stand_row"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemGapMmYes
itemWidthMmYes
insideWidthMmYes
labelEndReserveMmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds that the tool computes from measurements, implying a pure calculation, but gives no further behavioral context such as rounding rules, failure modes, or output format.

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 first sentence front-loads the computation and outputs with no filler. The standalone domain phrase and the fragment-like label-reserve sentence make it slightly choppy, but it remains brief.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-required-parameter calculator with no output schema, the description names the computed results but omits formulas, return format, and most parameter meanings. Annotations cover the safety profile, and the domain is simple, but invocation details remain thin.

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%, and the description only clearly maps one parameter through 'End reserve for price labels (mm)' for labelEndReserveMm. It implies usable row width and whole-item capacity relate to the other measurements, but does not explain how insideWidthMm, itemWidthMm, or itemGapMm are applied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Compute') and three outputs: usable row width, whole-item capacity, and remaining clearance. The domain phrase 'Trading card display stands' separates it from other row calculators, though it does not explicitly name a sibling alternative.

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?

There is no explicit when-to-use, when-not-to-use, or alternative guidance. The only usage clue is the trading-card display stand context, so the agent must infer that this is for row layout calculations for that product family.

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.