Skip to main content
Glama

The Doll Scout Home Tools

Estimate the rear riser · Rear shelf price labels

tds_shelf_price_label
Read-onlyIdempotent

Project a straight line from eye height to a rear detail past the front silhouette. Rear shelf price labels. Reading clearance (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": {
      "eyeHeightMm": "<eyeHeightMm>",
      "frontDistanceMm": "<frontDistanceMm>",
      "backDistanceMm": "<backDistanceMm>",
      "frontTopMm": "<frontTopMm>",
      "rearFeatureMm": "<rearFeatureMm>",
      "labelReadingMarginMm": "<labelReadingMarginMm>"
    },
    "name": "tds_shelf_price_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
frontTopMmYes
eyeHeightMmYes
rearFeatureMmYes
backDistanceMmYes
frontDistanceMmYes
labelReadingMarginMmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already establish that this is a safe read-only, idempotent, non-destructive operation in a closed world. The description adds the geometric projection concept and an output unit, but it does not explain assumptions, return format, or how the clearance is interpreted, so it adds only modest context beyond the annotations.

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 has no filler, but the middle sentence is a fragment and the geometric instruction is dense and jargon-heavy. It is concise yet poorly structured for quick comprehension.

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 six-parameter geometric calculation with no output schema, the description omits the return format, assumptions, units for most inputs, and interpretation of the result. 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?

Schema description coverage is 0%, so the description must explain six required integers. It loosely alludes to eye height, front/rear geometry, and reading clearance, but frontDistanceMm, backDistanceMm, frontTopMm, rearFeatureMm, and labelReadingMarginMm remain undefined in both schema and description.

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 an action ('Project a straight line from eye height to a rear detail past the front silhouette'), a domain ('Rear shelf price labels'), and an output unit ('Reading clearance (mm)'), so an agent can infer a sightline or visibility calculation. However, it never plainly says it estimates whether rear shelf price labels are readable, and it does not clearly differentiate from siblings such as tds_preflight_shelf_labels.

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 when-to-use guidance, no prerequisites, and no alternatives or exclusions. The only contextual hint is the phrase 'Rear shelf price labels,' leaving the agent to infer the appropriate scenario.

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.