Skip to main content
Glama

The Doll Scout Home Tools

Estimate the rear riser · A rear figurine’s face

tds_rear_figure_face
Read-onlyIdempotent

Project a straight line from eye height to a rear detail past the front silhouette. A rear figurine’s face. Visible gap above foreground (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>",
      "faceSightMarginMm": "<faceSightMarginMm>"
    },
    "name": "tds_rear_figure_face"
  }
}

Input Schema

NameRequiredDescriptionDefault
frontTopMmYes
eyeHeightMmYes
rearFeatureMmYes
backDistanceMmYes
frontDistanceMmYes
faceSightMarginMmYes

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?

The annotations already establish this as a safe, read-only, idempotent calculation, so the description does not need to repeat safety information. It adds that the tool projects a sightline and reports a visible gap in millimetres, but it does not explain assumptions, rounding, edge cases, or how the result should be interpreted.

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 not padded, but it is structured as fragmented sentences rather than a front-loaded explanation. “A rear figurine’s face.” and “Visible gap above foreground (mm).” add little clarity despite their brevity.

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?

This is a six-parameter calculation with no output schema, so the description should explain what is being estimated and what result is returned. It gives only a vague sightline description and an unexplained millimetre gap, leaving the definition substantially incomplete for the tool’s complexity.

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 the burden of explaining the six required parameters. It mentions eye height and a visible gap, but does not map meanings or units to frontDistanceMm, backDistanceMm, frontTopMm, rearFeatureMm, or faceSightMarginMm.

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 indicates a geometric projection from eye height to a rear detail, which is more specific than a bare restatement of the name, but the fragments “A rear figurine’s face” and “Visible gap above foreground (mm)” leave the actual estimate vague. It does not clearly distinguish this tool from siblings such as tds_figure_riser_row or tds_preflight_riser_placement.

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 guidance on when to use this tool, when not to use it, or which sibling tool is the alternative. The geometric phrasing implies a visibility or riser estimation context, but an agent must infer when this calculation is appropriate.

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.