Skip to main content
Glama
SorataYang

Qiao-MCP

by SorataYang

manage_check_case_file

Open or save concrete check case files for bridge analysis. Specify an action, case name, or file path to load existing cases or store new ones.

Instructions

    Open or save a concrete check case file (打��或保存混凝土检算工况文件).

    Args:
        action: "open" (打开) or "save" (保存)
        name: Check case name; for "open", resolves to the default check data
              directory when file_path is empty (工况名称)
        file_path: Full path to the case file. For "open" it takes priority over
                   name; for "save" a non-empty value means save-as
                   (工况文件完整路径;保存时非空表示另存为)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
actionYes
file_pathNo

Schema Changelog

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

  1. First observedv0.3.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations are all false hints and provide no behavioral disclosure, so the description carries the burden. It does disclose file resolution priority and save-as behavior, but it does not mention overwrite semantics, what happens when the file does not exist, or whether the current check case is mutated.

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 block is compact, with each parameter explanation earning its place. The bilingual duplication is slightly redundant but not harmful.

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

Completeness3/5

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

For a 3-parameter tool with no output schema, the parameter behavior is well covered. Still missing are return/error behavior and explicit guidance distinguishing this from model-file and check-stirrup siblings, which leaves selection context incomplete.

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?

The schema contains 0% description coverage, yet the description fully documents all three parameters: action values, name's default-directory behavior, and file_path's priority or save-as meaning. This adds substantial meaning that the schema alone does not provide.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description starts with 'Open or save a concrete check case file', using specific verbs and a concrete resource. It is clear enough to distinguish from model-level file tools like open_model_file/save_model_file, though it does not explicitly name those siblings.

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

Usage Guidelines3/5

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

It explains how to choose between 'open' and 'save' and how file_path/name interact, which is useful invocation guidance. However, it never states when this tool should be used instead of alternatives such as open_model_file, save_model_file, or manage_check_stirrup.

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