Skip to main content
Glama
SorataYang

Qiao-MCP

by SorataYang

assign_element_stirrup

Assign or remove shear and torsion stirrups on structural elements using predefined stirrup IDs, enabling reinforcement setup or cleanup in bridge models.

Instructions

    Assign or remove element stirrups (指定或删除单元箍筋).

    Stirrup numbers refer to definitions created by add_check_stirrup.
    箍筋号引用 add_check_stirrup 创建的箍筋定义。

    Args:
        action: "shear" (抗剪箍筋), "torsion" (抗扭箍筋), or "remove" (删除)
        element_id: Element ID (单元号); for "remove", <=0 removes all elements
        stirrup_i_y: I-end vertical stirrup ID, shear only (I端竖向箍筋号)
        stirrup_i_x: I-end transverse stirrup ID, shear only (I端横向箍筋号)
        stirrup_j_y: J-end vertical stirrup ID, shear only (J端竖向箍筋号)
        stirrup_j_x: J-end transverse stirrup ID, shear only (J端横向箍筋号)
        stirrup_i: I-end stirrup ID, torsion only (I端抗扭箍筋号)
        stirrup_j: J-end stirrup ID, torsion only (J端抗扭箍筋号)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
stirrup_iNo
stirrup_jNo
element_idNo
stirrup_i_xNo
stirrup_i_yNo
stirrup_j_xNo
stirrup_j_yNo

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?

The description discloses the important destructive behavior: for action 'remove', element_id <= 0 removes all elements. This is valuable because annotations provide no destructiveHint and readOnlyHint is false. It does not describe overwrite semantics or other side effects, which prevents a higher score.

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 front-loaded with the core action, then gives essential context, then a structured parameter list. Every line earns its place, including the bilingual annotations which clarify terminology rather than pad the text.

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 complex 8-parameter tool with no output schema, the description covers all parameters, action modes, the remove-all sentinel, and the relationship to add_check_stirrup. It leaves some ambiguity about which parameters are effectively required per action, though schema defaults partially mitigate this.

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%, but the description defines every parameter's role, the valid action values, and which stirrup IDs apply to shear vs torsion. It fully compensates for the empty schema and adds meaning well beyond the parameter names.

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+resource: 'Assign or remove element stirrups'. It also anchors stirrup numbers to definitions created by add_check_stirrup, which distinguishes this tool from that sibling and clarifies exactly what the tool operates on.

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 explicitly documents the three action modes ('shear', 'torsion', 'remove') and labels each parameter as shear-only or torsion-only, giving clear context for how to use the tool. It does not name alternative tools for when not to use it, 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