Skip to main content
Glama
SorataYang

Qiao-MCP

by SorataYang

manage_check_stirrup

Update or remove stirrup definitions for bridge code checking, adjusting type, dimensions, and spacing to align reinforcement models with design requirements.

Instructions

    Update or remove a stirrup definition (修改或删除检算箍筋定义).

    Use add_check_stirrup to create one. Lengths are in METERS (SI), converted
    internally. 新增请用 add_check_stirrup;长度入参为米,内部换算。

    Args:
        action: "update" (修改) or "remove" (删除)
        stirrup_id: Stirrup definition ID (箍筋定义编号); <=0 means match by name
        name: Stirrup definition name (箍筋定义名称)
        stirrup_type: 1=普通箍筋 (normal), 2=螺旋式箍筋 (spiral)
        material_id: Rebar material ID (钢筋材料号)
        limbs_number: Limbs, for normal stirrups (普通箍筋肢数)
        loops_number: Loops, for spiral stirrups (螺旋式箍筋环数)
        diameter: Stirrup diameter in meters (箍筋直径, 单位 m)
        spacing: Stirrup spacing in meters (箍筋间距, 单位 m)
        core_diameter: Spiral core diameter in meters (螺旋箍筋核心直径, 单位 m)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
actionYes
spacingNo
diameterNo
stirrup_idNo
material_idNo
limbs_numberNo
loops_numberNo
stirrup_typeNo
core_diameterNo

Schema Changelog

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

  1. First observedv0.3.1

TDQS

A3.8/5.0
Behavior1/5

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

The description explicitly includes a 'remove' action, which is a destructive operation, but annotations declare destructiveHint=false. This is a direct contradiction between the description and the structured annotation, so the score must be 1. Apart from that, it does usefully disclose internal meter conversion and the ID<=0 name-matching rule, but the contradiction dominates.

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 front-loaded with the purpose, then the creation-tool pointer, then a units note, followed by a complete Args block. It is longer than strictly necessary because it is bilingual, but the bilingual content is not pure padding and the structure is easy to scan.

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

Completeness2/5

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

With 10 parameters and no output schema, the description should clarify which fields are needed for 'update' versus 'remove', what happens when both stirrup_id and name are supplied, and what the call returns or whether removal is irreversible. It does not address these, leaving meaningful gaps for an agent deciding how to invoke the 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?

Schema description coverage is 0%, so the description must compensate, and it does thoroughly. Every parameter gets a Chinese/English meaning, units are specified in meters, stirrup_type codes are decoded as 1=normal/2=spriral, and the ID<=0 match-by-name behavior is explained. This is exactly the semantic value the schema lacks.

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 a specific verb and resource: 'Update or remove a stirrup definition', and it names the sibling add_check_stirrup as the creation tool. This lets an agent distinguish it from add_check_stirrup and assign_element_stirrup without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says 'Use add_check_stirrup to create one' and repeats this in Chinese ('新增请用 add_check_stirrup'), which tells the agent when not to use this tool. This is direct when/when-not guidance that routes to the correct sibling.

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