Create a new empty ETABS model without predefined grids or levels, specifying units for the project.
Crea un modelo vacio, sin ejes ni niveles predefinidos.
| Name | Required | Description | Default |
|---|---|---|---|
| units | No | Ton_m_C |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations and the description does not disclose any side effects, such as whether it replaces the current model, requires an active connection, or affects unsaved work. This is a critical gap for a potentially destructive action.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single concise sentence with no unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description lacks essential context about the operation's broader effects, such as interaction with the current model state, file handling, and return value.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single 'units' parameter is undefined in the schema and not mentioned in the description, leaving its purpose, allowed values, and impact completely unexplained.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it creates an empty model without predefined axes or levels, specifying the action and resource. It lacks explicit differentiation from siblings but the added detail helps distinguish it from a standard new model.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not provide guidance on when to use this tool versus alternatives like etabs_new_model, nor does it mention prerequisites or conditions for use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.