Skip to main content
Glama

Create track

create_track

Creates the track superstructure of one track on an IfcAlignment in one call and answers with the effect report; dry_run previews it with its checks, nothing written. In this order: rails (IfcRail, cut at the cant ramps), sleepers (IfcTrackElement from the type map, rolled with the cant), the bed (IfcCourse), each in ContainedInStructure (an IfcRailwayPart), typed by the named types, positioned by the alignment. Every size is named; nothing is taken for you. Checked after the build: gauge by ray, rail foot to sleeper, sleepers in the bed (net volume only then). A track stopped by the time budget between whole parts, rail pieces or sleeper blocks answers continue, the finished create_track call for the rest: send it as it stands. Repeated over a built range: track_range_occupied, nothing written. 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": {
      "track": "<track>",
      "ContainedInStructure": "<ContainedInStructure>"
    },
    "name": "create_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoYour note, stored with the new revision
trackYesOne track along the alignment from from_station_m to to_station_m
dry_runNoPreview: the planned effect and its checks, nothing written
request_idNoYour id for this call: a repeat answers the first result and writes nothing
ContainedInStructureYesThe IfcRailwayPart the parts stand in, Name or GlobalId

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare this is a write operation that is not read-only and not idempotent. The description adds substantial behavior beyond that: build order, post-build checks (gauge, rail foot to sleeper, sleepers in bed), time-budget continuation, range-occupancy rejection with nothing written, and a new revision on success. It does not detail permissions or the contents of the effect report, but it carries much of the behavioral burden.

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 purpose is front-loaded, but the remainder is a dense, run-on sequence with cryptic phrasing such as 'A call that succeeds is not a job that's done.' Most sentences carry technical information, but the structure and readability suffer.

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?

For a complex nested tool with no output schema, the description covers creation order, validation checks, dry-run behavior, partial continuation, and a key failure case. It could say more about the effect report's contents, but it is largely complete for correct invocation.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, so parameter meaning is largely covered there. The description adds only marginal cross-parameter context, such as the ContainedInStructure relationship and 'every size is named', without explaining individual parameter syntax or constraints beyond the schema.

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 states a specific verb and resource: creates the track superstructure of one track on an IfcAlignment in one call. It is clearly distinct from sibling tools like create_alignment or create_turnout, but it never explicitly names alternatives or explains how to choose between them.

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?

Usage is implied: use dry_run to preview, send the returned continue call to finish a time-budget stop, and expect track_range_occupied for repeated ranges. There is no explicit guidance on when to prefer this over sibling creation tools or when not to use it.

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