Skip to main content
Glama

The Doll Scout Home Tools

Check vertical clearance · Travel case top layer

tds_travel_tray_height
Read-onlyIdempotent

Compare measured opening height with the item, the stand or base and the working clearance. Travel case top layer. Required uncompressed lid gap (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": {
      "openingHeightMm": "<openingHeightMm>",
      "itemHeightMm": "<itemHeightMm>",
      "baseHeightMm": "<baseHeightMm>",
      "lidCompressionGapMm": "<lidCompressionGapMm>"
    },
    "name": "tds_travel_tray_height"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseHeightMmYes
itemHeightMmYes
openingHeightMmYes
lidCompressionGapMmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, closed-world, non-destructive operation. The description adds that it compares measured opening height against the item, base, and working clearance and mentions the uncompressed lid gap in mm, but it does not explain the comparison logic or what result is returned.

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 definition is short and front-loads the comparison action. The fragmentary sentences are terse rather than verbose, though the structure could be slightly clearer and more complete.

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-parameter read-only check with no output schema, the description gives the core comparison inputs but not the expected return value or pass/fail interpretation. It also leaves explicit usage guidance unstated, so meaningful context for invoking and interpreting the tool remains missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 reasonably maps the four required values to measured opening height, item, stand or base, and required uncompressed lid gap in mm, though it does not clarify whether baseHeightMm already includes the stand or exactly how 'working clearance' relates to lidCompressionGapMm.

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?

The description uses the specific verb 'Compare' and names the resources involved: opening height, item, stand or base, and working clearance. The scope 'Travel case top layer' helps distinguish it from generic drawer, stacked-tray, or carry-case checks, though no sibling alternative is named.

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?

The phrase 'Travel case top layer' provides an implied context for use, but the description does not explicitly say when to choose this tool over nearby clearance checks. It gives no exclusions or alternatives, so the agent must infer the intended situation from the title and scope.

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.