Skip to main content
Glama
SorataYang

Qiao-MCP

by SorataYang

create_nodes_linear

Create evenly spaced nodes along a straight line to model bridge girders. Specify count, starting point, and spacing instead of listing every coordinate.

Instructions

    Create evenly-spaced nodes along a straight line — the preferred way to model
    a bridge girder (等间距直线批量创建节点).

    Instead of listing 101 coordinates for a 100m span at 1m intervals, just specify
    the count, starting point, and spacing in each direction.

    Args:
        count: Number of nodes to create (节点数量)
        start_x: X coordinate of the first node (起点X坐标)
        start_y: Y coordinate of the first node (起点Y坐标)
        start_z: Z coordinate of the first node (起点Z坐标)
        spacing_x: X increment between nodes, m (相邻节点X方向间距)
        spacing_y: Y increment between nodes (相邻节点Y方向间距)
        spacing_z: Z increment between nodes (相邻节点Z方向间距)
        start_id: Requested ID of the first node (期望的起始节点编号).
                  HONORED ONLY when the model has no conflicting IDs — the
                  backend assigns its own numbering when start_id is taken.
                  The returned message reports the IDs actually assigned;
                  always trust those, not start_id.
                  (编号可能被后端改派,请以返回消息中的实际编号为准)
        is_merged: Whether to merge duplicate nodes (是否合并重合节点).
                   When merging occurs, fewer nodes are created than requested.
        merge_error: Merge tolerance, default 1e-3 (合并容差)

    Examples:
        # 100m simply-supported beam, 101 nodes at 1m pitch along X axis:
        create_nodes_linear(count=101, start_x=0, spacing_x=1.0)

        # Two-span 50m+50m continuous beam, start x from 0:
        create_nodes_linear(count=101, start_x=0, spacing_x=1.0)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
start_xNo
start_yNo
start_zNo
start_idNo
is_mergedNo
spacing_xNo
spacing_yNo
spacing_zNo
merge_errorNo

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, the description discloses critical behavior: start_id is only honored when there are no conflicting IDs, the backend may reassign IDs, and the returned message should be trusted over start_id. It also explains that merging can result in fewer nodes than requested, which is valuable behavioral context not visible in the schema or annotations.

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 well-structured with an intro, Args section, and Examples, and it front-loads the core purpose. It is somewhat long due to bilingual repetition, and the two examples are nearly identical in their parameter usage, but the structure makes it easy for an agent to parse.

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 10-parameter tool with no output schema, the description covers all parameters, explains key edge cases (ID reassignment, node merging), and provides concrete examples. Nothing essential about how to call the tool correctly or interpret the result is missing.

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 provides no descriptions for any of the 10 parameters, so the description carries the full burden — and it succeeds. Each parameter is explained with both English and Chinese labels, and start_id and is_merged receive important caveats about reassignment and merging. This exceeds what the schema alone provides.

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 clearly states the tool creates evenly-spaced nodes along a straight line, with a concrete use case (modeling a bridge girder). This distinguishes it from generic node creation tools like create_nodes and from create_beam_elements_linear, which creates elements rather than nodes.

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: it is the preferred method for modeling a bridge girder and avoids listing many coordinates. It does not explicitly name the generic alternative create_nodes or state when NOT to use this tool, but the 'preferred way' framing and the coordinate-listing contrast provide adequate usage 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