Skip to main content
Glama

Create alignment

create_alignment

Creates one IfcAlignment (IFC4X3 only) from its layouts and answers with the effect report; no target, dry_run previews, nothing written. Layout and curve after the norm, aggregated to the IfcProject; no IfcSegmentedReferenceCurve. The report's alignment: segments with world ends and end directions read back, length_m, deviation_m per clothoid, station_equations with distance_m. Layouts later: edit_alignment. Elements on it: create_elements at_station, at_stations, along, between_stations. 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": {
      "alignment": "<alignment>"
    },
    "name": "create_alignment"
  }
}

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
alignmentYesThe layouts: start, start_direction_deg and horizontal, or tangent_points; vertical, cant and stationing as needed
attributesNoAttributes of the IfcAlignment
request_idNoYour id for this call: a repeat answers the first result and writes nothing

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?

Beyond the annotations (non-read-only, non-destructive, not idempotent), it discloses real behavioral traits: IFC4X3-only, no IfcSegmentedReferenceCurve, an effect report is returned, dry_run writes nothing, request_id replays the first result without writing, and the warning 'A call that succeeds is not a job that's done' signals downstream verification. The schema also mentions refusals (tangent_overlap, transition_longer_than_arc) that the description doesn't summarize. It is informative but telegraphic.

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?

Front-loaded and free of filler, but written as terse fragments ('no target', 'New revision, effect report', 'A call that succeeds is not a job that's done') that require parsing effort. It is compact yet not maximally clear; a little expansion would improve readability without waste.

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?

No output schema exists, so the description carries the burden of explaining the return, and it does: alignment segments with world ends and end directions, length_m, deviation_m per clothoid, station_equations with distance_m. Combined with the 100%-documented nested schema, an agent has nearly everything needed; only the refusal/validation behavior is left implicit.

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?

Schema description coverage is 100%, so the schema already documents every parameter and nested field. The description only adds that layouts are the inputs and that station_equations/distance_m appear in the report; it doesn't add syntax or constraints beyond the schema, so the baseline 3 applies.

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?

Opens with a specific verb and resource: 'Creates one IfcAlignment (IFC4X3 only) from its layouts and answers with the effect report.' It also distinguishes itself from edit_alignment (for later layout changes) and create_elements (for things placed on it). Some phrasing is opaque ('Layout and curve after the norm, aggregated to the IfcProject') rather than plainly stating scope, which keeps it short of a 5.

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 states the creation mode ('no target, dry_run previews, nothing written') and points to the follow-up tools edit_alignment and create_elements with their station arguments, which implies create-then-edit-then-place ordering. But it never says when NOT to call this (e.g. when an alignment already exists and should be edited instead), and the sibling routing is about next steps rather than choosing between creation tools.

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