Skip to main content
Glama

Create reinforcement

create_reinforcement

Lays reinforcement in one concrete host (reinforcement.host) and answers with the effect report; dry_run previews the laying and its echo, nothing written. One bar set (IfcReinforcingBar, n bodies) with its type, or a laying of stock mats (IfcReinforcingMesh), in the host REINFORCEMENT_UNIT; moves with the host. Bars: at most 2000, 1 km each, 40 km together, and bar metres times host corners 160000. Mesh: at most 800 mats in one laying, about 150 km of wire, counted in mats. Never changes an existing set, except reinforcement.replace: a bar set laid anew in its place, GlobalId kept. A laying is changed later with edit_reinforcement. The host itself: create_elements. 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": {
      "reinforcement": "<reinforcement>"
    },
    "name": "create_reinforcement"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoYour note, stored with the new revision
dry_runNoPreview: the planned effect, nothing written
request_idNoYour id for this call: a repeat answers the first result and writes nothing
reinforcementYesOne laying in one host: host, rule and the keys of that rule; the core checks every key against its rule

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: hard limits (2000 bars, 1 km per bar, 40 km total, 800 mats, ~150 km wire), 'Never changes an existing set, except reinforcement.replace', a new revision is written, and the warning 'A call that succeeds is not a job that's done'. Annotations only declare non-read-only/non-destructive, so this is the real load-bearing context.

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

Conciseness4/5

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

Front-loaded with purpose, then limits, then mutation semantics, then alternatives. Dense and slightly telegraphic ('counted in mats', 'moves with the host'), but every clause carries information and there is no filler.

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 very complex tool with a huge nested schema and no output schema, the description covers mutation behavior, limits, replace semantics, and revision effects. It only lightly gestures at the 'effect report' contents, which is the one gap given no output schema exists.

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% and every nested parameter is documented in the schema, so the baseline is 3. The description repeats the limit values and replace semantics that already appear in the schema, adding no new parameter-level meaning.

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?

States a specific verb and resource ('Lays reinforcement in one concrete host'), names the return ('answers with the effect report'), and differentiates from siblings by saying edit_reinforcement changes an existing set and create_elements creates the host itself.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: 'A laying is changed later with edit_reinforcement' and 'The host itself: create_elements', plus dry_run for previewing. Clear when-to-use and alternatives, though it never states an explicit exclusion case where this tool should be avoided entirely.

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