Skip to main content
Glama

The Doll Scout Home Tools

Estimate the rear riser · Race numbers on miniature cars

tds_miniature_race_number
Read-onlyIdempotent

Project a straight line from eye height to a rear detail past the front silhouette. Race numbers on miniature cars. Gap for the race number (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>",
      "numberOffsetMm": "<numberOffsetMm>"
    },
    "name": "tds_miniature_race_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
frontTopMmYes
eyeHeightMmYes
rearFeatureMmYes
backDistanceMmYes
numberOffsetMmYes
frontDistanceMmYes

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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description need not repeat it. The description does add one genuine behavioral fact the annotations lack: the result is a millimetre clearance value ('Gap for the race number (mm)'). It says nothing about the computation's assumptions, tolerance, or what happens with degenerate inputs.

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?

Three short sentences with no filler, so it is compact. But the ordering is poor: the operation, then a topical fragment that adds nothing actionable, then the output buried last, making the definition read as scattered notes rather than a front-loaded explanation.

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 calculator with zero schema coverage and no output schema, the description should explain the projection model and each input's role. It supplies neither the formula nor the parameter meanings, leaving the agent unable to choose correct values with confidence even though the annotations make invocation safe.

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 integer parameters, so the description carries the full burden and largely fails it. It obliquely echoes 'eye height' (eyeHeightMm) and a 'rear detail' (rearFeatureMm) and 'front silhouette' (frontTopMm/frontDistanceMm), but backDistanceMm and numberOffsetMm are never explained, and no units convention other than mm is stated for any input.

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 first sentence gestures at a geometric sightline computation ('Project a straight line from eye height to a rear detail past the front silhouette') and the last names the output ('Gap for the race number (mm)'), so the general intent is inferable. However, the middle fragment 'Race numbers on miniature cars' is a topic tag rather than a purpose statement, and nothing distinguishes this calculator from look-alike siblings such as 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 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 precondition, and no mention of any alternative tool or when this estimator rather than a sibling applies. The agent must guess the scenario (miniature-car diorama sightline clearance) entirely from the title and topical fragment.

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.