Skip to main content
Glama
Sign In
etabs-mcp

etabs-mcp

by LATINALU
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

etabs_areas

Retrieves area elements (slabs and walls) with their properties and boundary nodes from an ETABS model.

Instructions

Elementos area (losas y muros) con su propiedad y nudos de contorno.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
storyNo
offsetNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/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, but it only lists output content ('su propiedad y nudos de contorno') and does not state read-only behavior, pagination semantics, or how the optional story filter affects results. The absence of side-effect disclosure is a gap, though nothing contradicts the annotations.

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

Conciseness4/5

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

The description is a single compact sentence with no filler or repetition, and the core resource detail is front-loaded. It earns conciseness, though the brevity contributes to missing usage and behavioral information.

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

Completeness2/5

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

For a tool with three parameters, no annotations, and no action verb, the description is too thin. The presence of an output schema reduces the need to describe return values, but the agent still lacks when-to-use guidance, parameter semantics, and behavioral expectations.

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

Parameters1/5

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

Schema description coverage is 0% and the description says nothing about limit, story, or offset. The agent receives no help understanding that story filters by level or that limit/offset paginate results.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as area elements (slabs and walls) and specifies they carry a property and contour nodes, which helps distinguish it from siblings like etabs_area_sections or etabs_points. However, it is a noun phrase with no explicit verb, so the agent must infer that the tool retrieves/lists these elements rather than creating or modifying them.

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 about when to call this tool instead of related tools such as etabs_frames, etabs_points, etabs_area_sections, or etabs_define_slab/wall. There are no context cues, exclusions, or alternative suggestions.

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