Skip to main content
Glama
SorataYang

Qiao-MCP

by SorataYang

configure_check_analysis

Configure concrete-check analysis settings for bridge structural software. Set parameters for bearing capacity, shear, stress, crack width, and limit states to align code checks with project requirements.

Instructions

    Configure a concrete-check analysis setting group (配置混凝土检算分析设置).

    ⚠️ UNITS (单位): parameters in this tool use qtmodel's NATIVE units —
    **mm for lengths and MPa for stresses**, NOT the SI (m/Pa) used elsewhere
    in this server. qtmodel does not document these units; they are inferred
    from its defaults (e.g. protective_thickness=30.0 means 30 mm,
    fatigue_limit_steel_bar=145.0 means 145 MPa). Pass values accordingly.
    本工具参数沿用 qtmodel 原生单位(长度 mm、应力 MPa),与本服务器其余
    工具的 SI 约定不同;qtmodel 未标注单位,此结论由其默认值推断。

    Use get_check_data("<kind>_setting") to read current values first.
    建议先用 get_check_data 读取当前值,再按需覆盖。

    Args:
        kind: Setting group (设置类别):
            "normal_section_bearing" (正截面承载力):
                normal_section_bearing_calculation_type: 1=同比例变化 2=轴力不变
                    3=My不变 4=Mz不变 5=轴力与My不变 6=轴力与Mz不变 7=My与Mz不变
            "oblique_shear_bearing" (斜截面抗剪承载力):
                reinforcement_height_multiple, is_consider_as_simple_support,
                shear_strength_material_factor,
                oblique_section_shear_direction_type: 1=竖向(z) 2=横向(y) 3=双向
            "limit_state" (极限状态法):
                cal_fatigue, fatigue_limit_steel_bar (MPa),
                fatigue_limit_prestress (MPa), is_consider_as_simple_support,
                is_consider_construction_load
            "normal_stress" (正应力):
                aashto2020_normal_stress_rebar_type: 1=直钢筋/无交叉焊缝焊接钢丝网
                    2=高应力区带交叉焊缝的直焊接钢丝网,
                tendon_allowable_stress_amplitude (MPa),
                flange_web_slenderness_ratio,
                construction_stage_concrete_tensile_limit (MPa),
                service_combination3_concrete_tension_limit (MPa)
            "crack_width" (裂缝宽度):
                highway_environment_category_type (1~7 公路环境类别),
                railway_environment_category_type (1~6 铁路环境类别),
                railway_limit_environment_category_type (1~11 铁路限值环境类别),
                crack_setting_type: 1=0 2=0.10 3=0.15 4=0.20 5=0.25 6=禁止使用,
                clear_protective_thickness (mm), protective_thickness (mm),
                steel_bar_type: 1=带肋钢筋 2=光圆钢筋,
                effect_coefficient_type: 1=软件自动计算 2=用户指定,
                user_specified_effect_coefficient, is_epoxy_resin_rebar,
                is_welded_rebar_skeleton, mq_mg (活载/恒载弯矩比), exposure_coefficient
            "moment_curvature" (弯矩曲率):
                moment_curvature_type: 1=轴力P变化 2=弯矩M变化,
                moment_curvature_model_type: 1=双线性模型 2=理想弹塑性模型
            "bearing_curve" (承载力曲线):
                bearing_curve_count (计算点数),
                angle_between_m_and_y_axis (弯矩方向与y轴夹角), force_p (轴力P)
        settings: Parameter dict for the chosen kind; only pass what you change
                  (该类别的参数字典,只需传要修改的项)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYes
settingsYes

Schema Changelog

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

  1. First observedv0.3.1

TDQS

A4.4/5.0
Behavior4/5

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

The description goes beyond the minimal annotations by disclosing that the tool uses qtmodel's native units (mm/MPa), that these units are undocumented and inferred from defaults, and that callers should use get_check_data before overwriting. It does not specify whether unspecified settings are reset or how the tool behaves on failure, but the disclosed quirks are substantial.

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 well-organized: the unit warning is front-loaded, the read-first guidance is prominent, and each setting group is structured as a labeled list. The bilingual duplication adds length, but the content is dense and almost entirely necessary given the empty schema.

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 tool with deeply nested, heterogeneous parameters and no output schema, the description covers the parameter space and unit semantics thoroughly. However, it omits potential prerequisites such as whether setup_concrete_check must be called first, and it does not describe the success/error behavior or return value, so it is not fully complete.

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 the schema only defines 'kind' and a generic settings object. The description compensates fully by documenting every kind's valid parameters, their enum values, units, and Chinese labels, effectively serving as the complete parameter reference.

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: 'Configure a concrete-check analysis setting group', and enumerates seven exact setting kinds such as normal_section_bearing, oblique_shear_bearing, and limit_state. This is precise enough to distinguish it from sibling tools like configure_analysis, run_concrete_check, and get_check_data.

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 instructs the agent to read current values first via get_check_data and to pass only the settings being changed, which is valuable usage guidance. It does not explicitly state when to choose this tool over configure_analysis or setup_concrete_check, so it falls short of 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