Skip to main content
Glama
SorataYang

Qiao-MCP

by SorataYang

get_check_data

Read-onlyIdempotent

Query concrete-check data from an open check case by type, covering results, case info, reinforcement, and analysis settings. Returns paginated details for bridge structural analysis.

Instructions

    Query concrete-check data by kind (按类型查询混凝土检算数据).

    Read-only. Requires a check case to be open/imported first.
    只读工具;需先创建或打开检算工况。列表结果分页返回。

    Args:
        kind: What to query (查询类型):
            ── 结果 Results ──
            "stress" (应力信息, 可选 stress_type/name),
            "solve_status" (检算求解状态)
            ── 工况 Case ──
            "case" (检算工况, 可选 name), "basic_info" (检算基本信息),
            "materials" (材料信息), "load_table" (荷载表, 可选 combine_type/name),
            "section_property" (截面特性), "element_table" (单元表)
            ── 配筋 Reinforcement ──
            "reinforcement" (配筋数据), "stirrups" (箍筋定义),
            "shear_stirrup" (单元抗剪箍筋, 可选 element_id),
            "torsion_stirrup" (单元抗扭箍筋, 可选 element_id),
            "vertical_prestress" (竖向预应力), "tendon_section" (钢束截面)
            ── 分析设置 Analysis settings ──
            "normal_section_bearing_setting" (正截面承载力),
            "oblique_shear_bearing_setting" (斜截面抗剪承载力),
            "limit_state_setting" (极限状态法), "normal_stress_setting" (正应力),
            "crack_width_setting" (裂缝宽度), "moment_curvature_setting" (弯矩曲率),
            "bearing_curve_setting" (承载力曲线)
        element_id: Element ID for stirrup queries; omit for all (单元号,省略则查全部)
        stress_type: Stress combination type for kind="stress" (应力组合类型):
            非 AASHTO: 1=标准值组合, 2=频遇组合, 3=准永久值组合, 4=主力组合,
                      5=主加附组合, 6=施工组合, 7=主加特殊组合, 8=恒载作用,
                      9=预应力作用, 10~13=使用组合Ⅰ~Ⅳ, 14=永久作用组合
            AASHTO 2020: 1~4=使用组合Ⅰ~Ⅳ, 5=永久作用组合, 6=施工组合
        combine_type: Combination type for kind="load_table" (荷载表组合类型)
        name: Explicit display name; overrides stress_type/combine_type when set
              (指定组合显示名,非空时优先于类型序号)
        limit: Max items per page, default 100, max 500 (单页条数上限)
        offset: Pagination offset (分页偏移)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYes
nameNo
limitNo
offsetNo
element_idNo
stress_typeNo
combine_typeNo

Schema Changelog

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

  1. First observedv0.3.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds meaningful beyond-annotation behavior: the prerequisite that a check case must be opened first, explicit read-only restatement, and pagination behavior. No contradiction with annotations.

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?

Long but exceptionally well-structured: front-loaded with purpose and read-only note, then organized into clear categories (Results, Case, Reinforcement, Analysis settings) with compact separators. Every sentence and code block earns its place by carrying information absent from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter tool with no output schema and no enums, the description is complete: it covers all parameter semantics, allowed values, defaults, pagination, prerequisites, and scope of data returned per kind. An agent has everything needed to invoke this tool correctly.

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?

With 0% schema description coverage, the description fully compensates by defining every parameter: categorized kind values with Chinese translations, stress_type enumerations including AASHTO and non-AASHTO variants, name override logic, element_id scope, and limit/offset defaults and max. This is exemplary parameter documentation.

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 ('Query'), resource ('concrete-check data'), and selection dimension ('by kind'), clearly differentiating it from generic model-info and analysis-result siblings like get_model_info or get_analysis_results. The bilingual purpose line is immediately informative and unambiguous.

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?

Provides clear operational context: read-only, requires an open/imported check case, and returns paginated results. It does not explicitly name sibling alternatives or when-not-to-use scenarios, so it stops short of a 5, but the context is strong and actionable.

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