Skip to main content
Glama
SorataYang

Qiao-MCP

by SorataYang

get_model_data

Read-onlyIdempotent

Query structural model data by kind—entities, loads, groups, and stages—with paginated results for targeted retrieval.

Instructions

    Query model data by kind (按类型查询模型数据) — the single read tool for
    entities, loads, groups and stages. List results are paginated.

    Args:
        kind: What to query (查询类型):
            ── 实体 Entities ──
            "nodes" (节点, 可选 ids), "elements" (单元, 可选 ids),
            "materials" (材料), "sections" (截面列表),
            "section_detail" (截面详情, 需 sec_id, 可选 position 0=起端 1=末端),
            "section_shape" (截面形状, 需 sec_id),
            "section_property" (截面特性, 需 sec_id),
            "thickness" (板厚), "boundaries" (全部边界条件),
            "node_local_axis" (节点局部坐标), "constraint_equations" (约束方程),
            "effective_widths" (有效宽度), "reinforcement" (配筋数据)
            ── 组 Groups ──
            "structure_groups" (结构组名列表),
            "group_elements" (结构组内单元, 需 name),
            "group_nodes" (结构组内节点, 需 name)
            ── 荷载 Loads ──
            "load_cases" (荷载工况名), "nodal_force_loads" (节点力),
            "nodal_displacement_loads" (节点位移/沉降), "beam_element_loads" (梁单元荷载),
            "plate_element_loads" (板单元荷载), "initial_tension_loads" (初拉力),
            "cable_length_loads" (索长荷载), "pre_stress_loads" (预应力荷载),
            "node_masses" (节点质量), "tendon_properties" (钢束特性),
            "deviation_parameters" (制造偏差参数), "deviation_loads" (制造偏差荷载)
            ── 施工阶段 Stages ──
            "stages" (施工阶段名), "stage_elements" (阶段内单元, 需 stage_id),
            "stage_nodes" (阶段内节点, 需 stage_id), "stage_groups" (阶段内组, 需 stage_id)
        ids: Entity IDs for nodes/elements, int/list/range string "1to10" (编号)
        name: Group name, for group_elements/group_nodes (结构组名)
        sec_id: Section ID, for section_detail/section_shape/section_property (截面号)
        position: Tapered section end, for section_detail (变截面位置 0起/1末)
        stage_id: Stage ID, for stage_* kinds (施工阶段号)
        limit: Max items per page, default 100, max 500 (单页条数上限)
        offset: Skip count for pagination (翻页偏移)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNo
kindYes
nameNo
limitNo
offsetNo
sec_idNo
positionNo
stage_idNo

Schema Changelog

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

  1. First observedv0.3.1

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses important behavior: list results are paginated, limit has a max of 500, defaults are specified, and certain kinds require additional parameters. It also documents the special ids format including the '1to10' range string, adding real value beyond the schema.

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 logically organized into categories with consistent formatting. The length is substantial, but it is justified by the large enumeration of kind values; the bilingual repetition adds bulk but also clarity.

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?

All 8 parameters are covered with defaults, constraints, and kind-specific requirements, plus pagination behavior. Although there is no output schema, the 'List results are paginated' statement and detailed kind semantics give an agent enough context to call the tool correctly and anticipate the response shape.

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%, so the description carries the full burden for all 8 parameters. It defines every parameter, enumerates all 30+ kind values organized by category, specifies per-kind required arguments, and gives semantics for ids, name, sec_id, position, stage_id, limit, and offset.

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 uses a specific verb and resource ('Query model data by kind') and explicitly frames itself as 'the single read tool for entities, loads, groups and stages,' which clearly separates it from the many create/update sibling tools. It states exactly what domain it covers.

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 is the read tool for four model categories, and it enumerates all supported kind values so an agent knows what it can query. It does not explicitly name alternative read tools like get_analysis_results or get_model_info as when-not-to-use cases, so it stops short of full exclusion guidance.

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