Skip to main content
Glama
Sign In
etabs-mcp

etabs-mcp

by LATINALU
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

etabs_unlock_model

Unlock an ETABS model after analysis to resume editing. Removes the post-analysis lock that blocks further modifications.

Instructions

Desbloquea el modelo para poder seguir editandolo tras un analisis.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

The description explains the outcome (model becomes editable after analysis) and the context, but does not mention potential side effects or failure conditions. Given the simplicity of the action, this is adequate.

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 a single concise sentence that conveys all necessary information without redundancy or fluff.

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?

For a tool with no parameters and a straightforward action, the description provides enough context (unlock after analysis to edit) and does not require additional details about output or edge cases.

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

Parameters4/5

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

There are no parameters, so the description does not need to explain any. The baseline for 0 params is 4, and the description is self-contained without missing parameter information.

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 the action (unlocks), the resource (the model), and the purpose (to continue editing after analysis). It is specific and distinguishes itself from other ETABS tools that don't mention unlocking.

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?

The description implicitly provides a usage condition: after an analysis, before editing. This tells the agent when to invoke this tool, and no alternative unlocking tool exists among siblings, so no comparison is needed.

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