Skip to main content
Glama
nonead

nUR MCP Server

by nonead

movel_z

Control robot movement along the Y-axis by specifying the robot's IP address and desired distance in meters for precise positioning.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYes
distanceYes

Implementation Reference

  • The handler function for the 'movel_z' MCP tool. It connects to the UR robot at the given IP, retrieves the current TCP pose, adjusts the Z coordinate by the specified distance, executes a movel command, confirms the movement, and logs/generates a script representation of the command.
    @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)}")
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a movement command but doesn't disclose behavioral traits such as whether it's safe (e.g., collision risks), requires specific robot states (e.g., powered on), has rate limits, or what happens on failure (e.g., error responses). The description only covers basic action and parameters, leaving critical operational context unspecified.

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 appropriately sized with two sentences that directly explain the tool's purpose and parameters. It's front-loaded with the main action and avoids unnecessary details. However, the first sentence is slightly verbose in Chinese ('命令指定IP机器人的TCP沿Y轴方向移动'), and it could be more structured with bullet points or clearer separation of concepts.

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?

Given no annotations, no output schema, and low schema coverage (0%), the description is incomplete. It lacks information on behavioral context (e.g., safety, prerequisites), error handling, return values, and how it fits within the sibling toolset (e.g., vs. 'movel_x'). For a movement tool in a robotics context, this leaves significant gaps for an AI agent to use it correctly.

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

Parameters4/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. It adds meaning for both parameters: 'ip' is explained as the robot address, and 'distance' as the movement distance in meters. This clarifies units and purpose beyond the schema's generic titles ('Ip', 'Distance'). However, it doesn't detail constraints (e.g., valid IP formats, distance ranges).

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 clearly states the action ('命令指定IP机器人的TCP沿Y轴方向移动' - commands a robot at a specified IP to move its TCP along the Y-axis) and resource (robot). It distinguishes from siblings like 'movel_x' (X-axis) and 'movel' (general linear movement) by specifying Y-axis movement. However, it doesn't explicitly mention the robot type or system context beyond 'TCP'.

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 on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites (e.g., robot connection status), when not to use it (e.g., during unsafe conditions), or compare it to siblings like 'movel_x', 'movel_y', or 'movej'. Usage is implied through parameter descriptions but not explicitly stated.

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/nUR-MCP-SERVER'

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