Skip to main content
Glama
SorataYang

Qiao-MCP

by SorataYang

create_tendon_property

Create prestressed tendon property definitions for bridge models, specifying tendon type, duct, steel, area, friction, wobble, and anchorage slip to enable accurate structural analysis and code checking.

Instructions

    Create a tendon property definition (创建钢束特性).

    Args:
        name: Tendon property name (钢束特性名)
        material_name: Prestress steel material name, must exist
                       (钢材材料名,须已通过 create_material 创建)
        tendon_type: Tendon type (钢束类型): 0=pre-tension(先张),
                     1=post-tension(后张), 2=external(体外)
        duct_type: Duct type (孔道类型): 1=金属波纹管, 2=塑料波纹管,
                   3=铁皮管, 4=钢管, 5=抽芯成型
        steel_type: Steel type (钢材类型): 1=钢绞线(strand), 2=螺纹钢筋(threaded bar)
        area: Tendon area in m² (钢束面积), e.g. 0.00139 for 10Φ15.2 strands
        duct_diameter: Duct diameter in m (孔道直径)
        friction: Friction coefficient μ (摩阻系数), typically 0.20~0.30
        deviation: Wobble coefficient k (偏差系数), typically 0.0015
        anchorage_slip: Anchorage slip at each end in m (锚固滑移,两端相同), typ. 0.006
        steel_detail: Advanced override, raw qtmodel steel_detail list
                      (高级用法:直接给出原始 steel_detail 列表,覆盖上述四个参数;
                      钢绞线=[面积,孔道直径,摩阻,偏差],
                      螺纹钢筋=[直径,面积,孔道直径,摩阻,偏差,张拉方式])
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areaNo
nameYes
frictionNo
deviationNo
duct_typeNo
steel_typeNo
tendon_typeNo
steel_detailNo
duct_diameterNo
material_nameYes
anchorage_slipNo

Schema Changelog

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

  1. First observedv0.3.1

TDQS

A4.2/5.0
Behavior3/5

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

With all annotations false and no safety profile, the description carries the burden. It discloses the advanced override behavior (steel_detail overrides the four parameters) and the material-existence prerequisite, but does not explain duplicate-name behavior, validation, or return values. The override quirk is useful, but the side-effect contract remains under-specified.

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 long but front-loaded and dense: each parameter line adds units, examples, or codes absent from the schema. Bilingual repetition is verbose but functional for the locale.

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 an 11-parameter create operation with no output schema, this covers all inputs, preconditions, enum coding, and advanced override cases. It could add failure/duplicate behavior and return-value expectations, but nothing essential for selecting and invoking the tool is missing.

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 coverage is 0%, and this description compensates fully: it explains every parameter's meaning, enum values, units, typical values, and the steel_detail list format. Without it, the eleven schema entries would be bare names and defaults.

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 'Create a tendon property definition (创建钢束特性)', naming a specific verb and resource. The parameter context (prestress steel material, duct, tendon type) clearly distinguishes this from siblings like create_tendon_2d and add_tendon_3d by showing it defines property data, not geometry.

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?

It explicitly states that material_name must already exist and references create_material as the prerequisite, giving an agent a required precondition. It also labels steel_detail as an advanced override for special cases. It does not explicitly contrast with geometry/assignment siblings, so not a 5.

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