Skip to main content
Glama
SorataYang

Qiao-MCP

by SorataYang

add_to_structure_group

Add nodes and elements to an existing structure group in bridge structural analysis software, enabling efficient updates to model groupings without recreating them.

Instructions

    Add nodes and/or elements to an existing structure group
    (向已有结构组中添加节点和/或单元).

    Args:
        group_name: Name of the structure group (结构组名称)
        node_ids: Node ID(s) to add. Supports int, list, or range string '1to10'.
                  (要添加的节点编号)
        element_ids: Element ID(s) to add. Supports int, list, or range string.
                     (要添加的单元编号)

    Example:
        add_to_structure_group("上部结构", element_ids="11to20")
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_idsNo
group_nameYes
element_idsNo

Schema Changelog

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

  1. First observedv0.3.1

TDQS

A3.5/5.0
Behavior3/5

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

The description communicates an additive mutation to an existing group, which is consistent with the annotations. However, it does not explain behavior for edge cases such as nonexistent groups, duplicate IDs, or whether both node_ids and element_ids may be combined in a single call.

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 purpose is front-loaded and the Args section is compact and readable. The bilingual text adds some repetition but does not make the description unwieldy.

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?

The description covers the main purpose, parameter types, and an example, which is good for a simple tool. However, it omits prerequisites or error behavior, and the lack of explicit 'at least one of node_ids/element_ids' guidance leaves room for incorrect invocations.

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?

With 0% schema description coverage, the description compensates well by explaining that node_ids and element_ids support int, list, or range string like '1to10' and by providing a concrete example. It falls short of explicitly requiring at least one of node_ids or element_ids to be provided.

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 adds nodes and/or elements to an existing structure group, using a specific verb and resource. It is easy to understand, but it does not explicitly differentiate itself from the sibling tool add_elements_to_group.

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

Usage Guidelines3/5

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

The intended use is implied by the action and example, but the description does not explicitly state when to prefer this tool over alternatives such as add_elements_to_group or create_structure_group. No exclusions or prerequisites are mentioned.

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