Skip to main content
Glama
SorataYang

Qiao-MCP

by SorataYang

create_beam_element

Create a single beam, truss, or cable element by connecting start and end nodes with given material and section IDs. Set element type, beta angle, and initial strain or force as needed.

Instructions

    Create a single frame element (beam/truss/cable) with named parameters
    (创建单个梁/杆/索单元,参数具名).

    This is the preferred way to create individual elements — all parameters
    have explicit names and inline documentation.

    Args:
        node_i: Start node ID (I端节点编号)
        node_j: End node ID (J端节点编号)
        mat_id: Material ID — use get_materials to find valid IDs (材料编号)
        sec_id: Section ID — use get_section_list to find valid IDs (截面编号)
        element_id: Element ID, -1 = auto-assign next available ID (单元编号,-1表示自动分配)
        beta_angle: Beta angle in degrees, controls local axis orientation (贝塔角,度)
        ele_type: Element type (单元类型): 1=Beam(梁), 2=Truss(杆), 3=Cable(索)
        initial_type: Initial strain/force type (初始应变类型): 0=None, 1=Strain, 2=Force
        initial_value: Initial strain or force value (初始应变或内力值)

    Example:
        create_beam_element(node_i=1, node_j=2, mat_id=1, sec_id=1)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mat_idYes
node_iYes
node_jYes
sec_idYes
ele_typeNo
beta_angleNo
element_idNo
initial_typeNo
initial_valueNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.3.1

TDQS

A4.3/5.0
Behavior3/5

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

Annotations are all false, so they add little; the description provides useful behavioral details like element_id=-1 meaning auto-assign next available ID and that materials/sections must be looked up via get_materials/get_section_list. However, it does not disclose the return value, overwrite behavior, or model-state side effects beyond the act of creation.

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 front-loaded with the core action, then uses a structured Args block and a minimal example to make 9 parameters easy to scan. The bilingual notes and 'preferred way' sentence do not blout.

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

Completeness4/5

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

For a 9-parameter create tool with no output schema and no enum constraints, the description covers every parameter, gives valid value ranges, and tells the agent where to find material/section IDs. Minor gaps remain around the return value and duplicate/overwite behavior, but an agent can invoke it confidently.

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

Parameters5/5

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

Schema description coverage is 0%, so the description is the only source of parameter meaning. The Args block documents all 9 parameters, including ele_type and initial_type value maps, beta_angle units, and element_id auto-assign semantics. The example also provides a minimal valid call.

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 states a specific verb and resource: 'Create a single frame element (beam/truss/cable)' and distinguishes it from bulk/linear creation via the word 'single'. This clearly differentiates it from siblings like create_beam_elements_linear and create_elements.

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 explicitly says 'This is the preferred way to create individual elements,' which gives agents a clear condition for selecting this tool. It doesn't name alternatives or state when not to use it, so it stops just short of full exclusion guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SorataYang/qiao-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server