Skip to main content
Glama
mdvaleed7

ETABS MCP Server

by mdvaleed7

etabs_apply_aci_stiffness_modifiers

Idempotent

Apply ACI 318 stiffness modifiers to beams, columns, walls, and slabs in one call using object names or groups, with optional preset overrides.

Instructions

One-shot convenience: apply ACI 318 stiffness modifiers to beams, columns, walls, and slabs in a single tool call.

For each category, supply either an explicit *_names list OR a named ETABS *_group. Any category with neither is skipped.

Defaults (ACI 318-19 Table 6.6.3.1.1(a)):

  • Beams → I = 0.35 Ig, torsion = 0.20

  • Columns → I = 0.70 Ig, A = 0.70 Ag

  • Walls → I = 0.70 Ig, A = 0.70 Ag (uncracked)

  • Slabs → I = 0.25 Ig

Example — apply to all members via groups: beam_group="BEAMS", column_group="COLUMNS", wall_group="WALLS", slab_group="SLABS"

Example — apply to specific objects: beam_names=["B1","B2"], column_names=["C1","C2","C3"], wall_names=["W1"], slab_names=["S1","S2"]

Args: beam_names / column_names / wall_names / slab_names: Explicit lists of object names per category. beam_group / column_group / wall_group / slab_group: Named ETABS groups to apply each preset to. beam_preset / column_preset / wall_preset / slab_preset: Override the default ACI preset for any category. (See etabs_assign_frame_stiffness_modifiers and etabs_assign_area_stiffness_modifiers for the full preset list.)

Returns: JSON summary: per-category count + preset, plus grand totals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
beam_namesNo
column_namesNo
wall_namesNo
slab_namesNo
beam_groupNo
column_groupNo
wall_groupNo
slab_groupNo
beam_presetNoaci_beam
column_presetNoaci_column
wall_presetNoaci_wall
slab_presetNoaci_slab

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No contradictions with annotations; adds context about being a one-shot convenience and requiring either names or groups. Idempotent hint is supported by the description.

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

Conciseness5/5

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

Well-structured with sections, examples, and clear parameter breakdown; informative yet concise with no unnecessary details.

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

Completeness5/5

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

Covers all aspects: parameter modes (names vs. groups), defaults, outputs (JSON summary), and references to other tools for presets. Output schema exists but description sufficiently describes return values.

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

Parameters5/5

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

Despite 0% schema coverage, the description thoroughly explains all parameters, their roles, defaults, and provides examples, fully compensating for the lack of schema descriptions.

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 description clearly states it applies ACI 318 stiffness modifiers to beams, columns, walls, and slabs in a single call, distinguishing it from lower-level sibling tools like etabs_assign_frame_stiffness_modifiers.

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

Usage Guidelines5/5

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

Provides explicit examples for using names vs. groups, explains that categories with neither are skipped, and directs users to other tools for full preset lists.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mdvaleed7/ETABS-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server