Skip to main content
Glama

The Doll Scout Home Tools

Estimate the rear riser · A sleeved card’s text line

tds_card_face_detail
Read-onlyIdempotent

Project a straight line from eye height to a rear detail past the front silhouette. A sleeved card’s text line. Gap for the selected text line (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>",
      "cardTextMarginMm": "<cardTextMarginMm>"
    },
    "name": "tds_card_face_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
frontTopMmYes
eyeHeightMmYes
rearFeatureMmYes
backDistanceMmYes
frontDistanceMmYes
cardTextMarginMmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — no mention of how the projection is computed, what units the output is in, or what geometric assumptions (flat card, straight sightline) constrain the result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short fragments, and the middle one ("A sleeved card's text line") is a dangling noun phrase that conveys nothing actionable. It is brief but under-specified rather than concise — the length is achieved by omitting necessary content, not by trimming filler.

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

Completeness1/5

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

A six-parameter computational tool with no output schema, no parameter documentation, and no annotation-independent explanation of the math or return value. There is no way for an agent to know what number comes back or what the parameters mean in relation to each other, which is a critical gap for an estimator.

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% across six required parameters, so the description must carry the load and largely does not. Only two are loosely echoed (eyeHeightMm via "eye height", rearFeatureMm via "rear detail"), and "Gap for the selected text line (mm)" hints at cardTextMarginMm, but frontTopMm, frontDistanceMm and backDistanceMm are never explained and the "selected text line" phrasing implies a selection mechanism that no parameter exposes.

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

Purpose2/5

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

The description gestures at geometric projection ("Project a straight line from eye height to a rear detail past the front silhouette") but never states plainly that it computes a rear riser height or gap in millimetres. The title fragment "A sleeved card's text line" is a label, not an explanation, and nothing distinguishes it from siblings like tds_rear_figure_face or tds_figure_riser_row.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 (e.g. units, coordinate assumptions), and no named alternative among the many tds_* riser/card tools. An agent has no basis for choosing this tool over its siblings.

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.