Skip to main content
Glama

Create turnout

create_turnout

Creates the branch of a turnout as one IfcAlignment (IFC4X3) positioned by the stem (IfcRelPositions) and answers with the effect report; dry_run previews it, nothing written. With it, in the same revision, the turnout panel: one IfcElementAssembly TURNOUTPANEL at WA in ContainedInStructure (an IfcRailwayPart you name), positioned by stem and branch, no body, no parts; Moddl_Weiche holds the base form. radius_m, ratio_n and straight_m name the base form: from WA the branch leaves the stem tangent, an arc of radius_m until it stands at 1:n, then straight_m to WE; WM lies t = R tan(a/2) after WA, WE t + s after WM on both tracks, stations along the stem axis. On a stem of one circular arc from WA to WE the base form is bent (rule turnout_curvature_added: the stem curvature added to each row, lengths kept; deviation_m against the base ordinates square to the stem). Art EW, IBW or ABW is measured, the gradient taken from the stem (turnout_gradient_from_stem). moddl takes no catalogue: a stem with a transition, a change of radius, a cant or off one gradient from WA to WE is refused. The report's alignment.turnout: WA, WM, WE as stations, the frog where the running edges cross (with gauge_m; its crossing 1:n' beside the end 1:n), the junction gap and kink read back from the file (0). Tracks: create_track up to WA and from WE; the four rails WA-WE: create_track parts ['rails'] on stem and branch. Frog, blades, stock and check rails are not built. New revision, effect report. A call that succeeds is not a job that's done.

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": {
      "turnout": "<turnout>",
      "ContainedInStructure": "<ContainedInStructure>"
    },
    "name": "create_turnout"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoYour note, stored with the new revision
sourceNoWhere the values you write come from: assumption (default, your own estimate, stamped in the file) or user (only what the person named word for word; it then reads as the file does)
dry_runNoPreview: the planned effect, nothing written
turnoutYesThe turnout: stem, WA and the base form
attributesNoAttributes of the branch
request_idNoYour id for this call: a repeat answers the first result and writes nothing
ContainedInStructureYesThe IfcRailwayPart the panel stands in, Name or GlobalId

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent write, so the description does not need to restate safety. It adds real context beyond that: dry_run writes nothing, a new revision and effect report are produced, invalid stems are refused, and frog/blades/stock/check rails are explicitly not built.

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?

The description is a dense, run-on paragraph of extreme length with jargon and semicolon-chained clauses. Though the purpose is front-loaded, the structure is poor and much of the geometry/report detail could be shortened or bulleted for readability.

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

Completeness4/5

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

Given a complex mutation tool with no output schema, the description is thorough: it explains created objects, dry-run behavior, refusal cases, and the report's alignment.turnout fields. Some phrasing remains cryptic, but the major behavioral and output expectations are covered.

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 coverage is 100%, so the baseline is 3. The description goes beyond the schema by tying radius_m, ratio_n, and straight_m to the turnout base form geometry and explaining how WM and WE are computed, which helps an agent understand the parameter relationships.

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

Purpose5/5

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

The opening states a specific verb and resource: 'Creates the branch of a turnout as one IfcAlignment (IFC4X3) positioned by the stem (IfcRelPositions)' and also names the turnout panel created. This distinguishes it from generic siblings like create_alignment or create_track.

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?

It gives workflow guidance ('create_track up to WA and from WE') and refusal conditions ('moddl takes no catalogue: a stem with a transition ... is refused'), but never explicitly says when to choose this tool over create_alignment or edit_alignment. Usage is implied rather than stated as an alternative-selection rule.

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.

Resources