Skip to main content
Glama
SorataYang

Qiao-MCP

by SorataYang

create_tendon_2d

Create a 2D tendon profile in the X-Z plane using control points and fillet radii. Define the insertion point and tendon properties to build bridge models for structural analysis.

Instructions

    Create a 2D tendon defined by profile control points (创建2D钢束/平弯钢束).

    The tendon profile lies in the X-Z plane; each control point is
    [x, z, r] where r is the fillet radius (0 for sharp points).
    钢束线形位于XZ平面,控制点为 [x, z, r],r为圆弧半径(0为折点)。

    Args:
        name: Tendon name (钢束名称)
        property_name: Tendon property name, must exist (钢束特性名,须已创建)
        control_points: Profile control points [[x, z, r], ...]
                        (控制点信息 [[x, z, 半径r], ...])
        point_insert: Insertion point [x, y, z] for straight positioning
                      (直线定位时的插入点坐标 [x, y, z])
        num: Number of tendons (根数)
        line_type: Point type (线型): 1=导线点(guide), 2=折线点(polyline)
        position_type: Positioning (定位方式): 1=straight(直线), 2=track line(轨迹线)
        symmetry: Symmetry point (对称点): 0=left end(左端), 1=right end(右端),
                  2=asymmetric(不对称)
        group_name: Tendon group name (钢束组名)

    Example:
        create_tendon_2d(name="T1", property_name="15-10",
                         control_points=[[0, -0.5, 0], [20, -1.2, 8], [40, -0.5, 0]],
                         point_insert=[0, 0, 0])
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numNo
nameYes
symmetryNo
line_typeNo
group_nameNo默认钢束组
point_insertYes
position_typeNo
property_nameYes
control_pointsYes

Schema Changelog

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

  1. First observedv0.3.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations are all false, so the description carries the burden of behavioral disclosure. It provides meaningful behavioral detail: the tendon profile lies in X-Z, control points are [x,z,r] with fillet radius semantics, property_name must already exist, and positioning modes are explained. It does not state return values or error behavior, but for a create tool the main behavioral surface is well covered.

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 well organized: one-line summary, geometry explanation, parameter list, and an example. Every sentence adds value, and the key distinguishing facts are front-loaded before the parameter details.

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 tool with no output schema and no schema-level descriptions, the description covers all parameters and gives an example. Minor gaps remain: the interplay between point_insert and position_type=2 (track line) is not fully explained, and return/error behavior is not mentioned.

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%, yet the description documents all 9 parameters with meanings, coordinate formats, allowed values for line_type/position_type/symmetry, and a concrete example. This fully compensates for the empty schema descriptions.

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 opens with a specific verb and resource: 'Create a 2D tendon defined by profile control points.' It clearly distinguishes this from sibling tools like add_tendon_3d by stating the profile lies in the X-Z plane and refers to 2D/平弯钢束.

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 gives clear context: this tool creates a 2D tendon in the X-Z plane, and it notes that property_name must already exist (须已创建), which is a prerequisite. It does not explicitly say 'use add_tendon_3d for 3D tendons,' but the 2D vs. 3D distinction is strongly implied by the plane definition.

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