etabs-mcp

Overview Schema Source Related Servers Discussions Admin

etabs_new_model

Creates a new ETABS model with a regular grid and specified story levels. Discards the current unsaved model, so save existing work first.

Instructions

Crea un modelo nuevo con una retícula regular y los niveles indicados.

Descarta el modelo abierto sin guardar, asi que guarda antes con etabs_save_model.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "etabs_new_model"
  }
}

Input Schema

Name	Required	Default
`units`	No	Ton_m_C
`stories`	No
`spacing_x`	No
`spacing_y`	No
`grid_lines_x`	No
`grid_lines_y`	No
`story_height`	No
`bottom_story_height`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It clearly states that the tool discards the open model without saving, a critical destructive trait. This is essential information, though it does not cover other potential behaviors like unit reset or return format.

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?

The description is two sentences with zero redundancy. The first sentence states the core function, and the second delivers a crucial warning. It is front-loaded and efficient, with every word earning its place.

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

Completeness3/5

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

The description covers the primary purpose and the key destructive warning, but it is incomplete for a tool with 8 parameters. It does not explain parameter meanings, nor does it mention the output schema or any post-creation behavior. An agent would need additional context to correctly configure the model parameters.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, but it provides no explanation of the 8 parameters. While some names like 'stories' and 'spacing_x' are self-explanatory, others like 'bottom_story_height' and 'units' are not clarified. The description adds no semantic value beyond the schema's basic names.

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 the verb 'Crea' (creates) and the resource 'un modelo nuevo' (a new model) with a regular grid and indicated levels. It clearly conveys the tool's function, but does not explicitly differentiate it from sibling etabs_new_blank_model, relying on the 'regular grid' and 'levels' detail to imply distinction.

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?

The description provides a clear prerequisite: save the current model before using this tool, because it discards the open model without saving. This is explicit guidance on when to use it (after saving) and implicitly warns against using it without saving, though it does not mention alternatives like etabs_new_blank_model.

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

Deploy Server