Skip to main content
Glama
nonead

Nonead Universal-Robots MCP Server

by nonead

movel_z

Move the robot's TCP along the Y axis by a specified distance. Provide the robot's IP address and distance in meters.

Instructions

命令指定IP机器人的TCP沿Y轴方向移动 IP:机器人地址 distance:移动距离(米)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYes
distanceYes

Implementation Reference

  • The movel_z tool handler: takes an IP address and a distance (in meters), gets the current TCP pose, adds the distance to the Z-axis component (pose[2]), sends a movel command to the robot, waits for confirmation, and returns the result.
    @mcp.tool()
    def movel_z(ip: str, distance: float):
        """命令指定IP机器人的TCP沿Y轴方向移动
        IP:机器人地址
        distance:移动距离(米)"""
        try:
            if '连接失败' in link_check(ip):
                return return_msg(f"与机器人的连接已断开。")
            pose = robot_list[ip].get_actual_tcp_pose()
            pose[2] = pose[2] + distance
            robot_list[ip].movel(pose)
            time.sleep(1)
            result = movelConfirm(ip, pose)
            cmd = (f"def my_program():\n"
                   f"  movel(p[{'{:.4f}'.format(pose[0])},{'{:.4f}'.format(pose[1])},{'{:.4f}'.format(pose[2])},{'{:.4f}'.format(pose[3])},{'{:.4f}'.format(pose[4])},{'{:.4f}'.format(pose[5])},],0.5,0.25,0,0)\n"
                   f"end\nmy_program()")
            logger.info(f"发送脚本:{cmd}")
            if result == 1:
                return return_msg(f"命令 {cmd} 已发送,移动完成。")
            else:
                return return_msg(f"命令 {cmd} 已发送,移动失败。")
        except Exception as e:
            logger.error(f"移动失败: {str(e)}")
            return return_msg(f"移动失败: {str(e)}")
  • Registration of movel_z as an MCP tool via the @mcp.tool() decorator on the FastMCP instance 'mcp'.
    @mcp.tool()
  • Helper function movelConfirm used by movel_z to verify that the movel movement completed successfully.
    def movelConfirm(ip, pose):
        """
        movel移动的结果确认
        1:移动到位
        2:移动结束,但是位置不准确
        """
        loop_flg = True
        count = 0
        while loop_flg:
            time.sleep(1)
            current_pose = round_pose(robot_list[ip].get_actual_tcp_pose())
            if right_pose_tcp(current_pose, pose):
                robot_list[ip].robotConnector.DashboardClient.ur_running()
                running = robot_list[ip].robotConnector.DashboardClient.last_respond
                if running == 'Program running: false':
                    return 1
            else:
                robot_list[ip].robotConnector.DashboardClient.ur_running()
                running = robot_list[ip].robotConnector.DashboardClient.last_respond
    
                if running == 'Program running: true':
                    '''尚未移动完成'''
                    continue
                else:
                    '''移动完成'''
                    count = count + 1
                    if count > 5:
                        return 2
Behavior1/5

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

The description contradicts the tool name regarding the axis of movement, which is a serious behavioral inconsistency. Additionally, no information is given about safety, speed, units (beyond distance being meters), or side effects. With no annotations, this is inadequate.

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 very short (two sentences), which is appropriate for a simple parameterized command. However, the structure could be improved by separating the action from parameter documentation more clearly. It is concise but not perfectly structured.

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

Completeness1/5

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

Given the existence of sibling tools for movel_x and movel_y, this tool should distinctly handle Z-axis movement, but the description incorrectly mentions Y-axis. No output schema or additional behavioral context is provided, making it incomplete for an agent to use effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning beyond the bare schema: it clarifies that 'ip' is the robot address and 'distance' is in meters. However, this is minimal and does not address the axis discrepancy. For a tool with 0% schema description coverage, this provides baseline clarity but no extra depth.

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

Purpose2/5

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

The description states it moves the TCP along the Y-axis, but the tool name 'movel_z' implies Z-axis movement. This contradiction causes confusion about the actual purpose. It does specify a verb and resource but with incorrect axis.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus sibling tools like movel_x or movel_y. The description gives no context for differentiation, forcing the agent to rely on the name alone, which is unreliable due to the axis mismatch.

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/nonead/Nonead-Universal-Robots-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server