Skip to main content
Glama
SorataYang

Qiao-MCP

by SorataYang
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

create_elements

Create structural elements (beam, truss, cable, plate) from raw data arrays, specifying material, section, and connectivity properties.

Instructions

    Create elements from a raw data array (通过原始数组创建单元).

    For beam elements, prefer `create_beam_element` or `create_beam_elements_linear`
    which have named parameters and are easier to use correctly.

    Args:
        element_data: Element data list. Each item format:
            - Beam/Truss: [id, type(1=beam,2=truss), matId, secId, beta, nodeI, nodeJ, initType, initVal]
            - Cable:      [id, 3, matId, secId, beta, nodeI, nodeJ, tensionType, tensionVal]
            - Plate:      [id, 4, matId, thicknessId, beta, nodeI, nodeJ, nodeK, nodeL, plateType]
            单元数据列表。梁=1, 杆=2, 索=3, 板=4

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
element_dataYes

Schema Changelog

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

  1. First observedv0.3.1

TDQS

A4/5.0
Behavior3/5

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

Annotations are all false, so the description carries the burden. It discloses that this is a low-level raw-array creation routine and hints it is error-prone for beams by pointing to easier alternatives. However, it does not state prerequisites such as existing nodes/materials/sections, whether elements are appended or overwritten, or failure behavior.

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 front-loaded with purpose, then usage preference, then structured bullet formats. The bilingual type-code sentence is slightly redundant, but the content is otherwise tight and well-orgnized.

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 complex bulk-creation tool with no output schema and empty item schemas, it provides enough to construct the argument array. It omits prerequisites, return behavior, and validation behavior, which are meaningful gaps for correct invocation.

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?

Schema coverage is 0% because element_data items are empty arrays, and the description compensates with detailed list formats for beam/truss, cable, and plate including type codes. It does not define every field such as beta, initType, or tensionType, but the field names are mostly self-explanatory.

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?

States a specific action ('Create elements') and resource ('raw data array'), enumerates supported element types (beam, truss, cable, plate), and names sibling alternatives for beam elements. This makes it distinguishable from create_beam_element and create_beam_elements_linear without opening their schemas.

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?

Explicitly advises preferring create_beam_element or create_beam_elements_linear for beam elements, giving a clear when-not-to-use signal. It does not explicitly state 'use this for cable/plate/bulk raw data', but the raw-array intro and format list imply those cases.

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