Skip to main content
Glama
Sign In
etabs-mcp

etabs-mcp

by LATINALU
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

etabs_save_model

Save the current ETABS model. Provide an absolute .edb path to perform a 'save as' to a new file location.

Instructions

Guarda el modelo. Con path hace 'guardar como' (usa ruta absoluta .edb).

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_save_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It mentions that providing a path performs 'save as' and advises using an absolute .edb path, but it does not disclose side effects such as overwriting an existing file or behavior when path is omitted.

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 extremely concise—two short sentences—and immediately conveys the core purpose. No filler or unnecessary detail.

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?

For a simple save operation, the description covers the main action and the path variant, but it omits explicit mention that the tool saves the current model, potential errors, or output details. It is adequate but not richly complete.

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?

The single 'path' parameter is described as enabling 'save as', which adds meaning beyond the raw schema. However, it does not clarify the default behavior when path is not provided, leaving part of the semantics ambiguous.

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 clearly states the tool saves the model, identifying the action and resource. It is distinct from sibling tools like open_model or new_model, though it does not explicitly mention 'current model'.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives, and there is no mention of prerequisites (e.g., an open model). The path option is mentioned but not framed within a usage context.

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

Deploy Server

Other Tools