Skip to main content
Glama
nonead

nUR MCP Server

by nonead

movel_y

Control robot movement along the Y-axis by specifying IP address and distance in meters. This tool enables precise positioning for Universal Robots through the nUR MCP Server.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYes
distanceYes

Implementation Reference

  • The main handler function for the 'movel_y' MCP tool. It connects to the UR robot via IP, retrieves current TCP pose, adjusts the Y-coordinate by the specified distance, executes a linear move (movel), confirms the move was successful using movelConfirm, and logs/generates a script command for the move.
    @mcp.tool()
    def movel_y(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[1] = pose[1] + 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?

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the action (move TCP along Y-axis) but doesn't describe what happens during execution (e.g., blocking/non-blocking, safety considerations, error conditions, or what 'TCP' refers to in this context). For a robot control tool with zero annotation coverage, this leaves significant behavioral gaps.

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 brief (two sentences) and front-loaded with the main purpose. Each sentence adds necessary information about parameters, though the structure could be slightly improved with clearer separation between purpose and parameter explanations.

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?

For a robot movement tool with no annotations, no output schema, and 0% schema description coverage, the description is inadequate. It doesn't explain what 'TCP' means (Tool Center Point), doesn't mention coordinate frames, doesn't describe movement characteristics (speed, acceleration), and provides no information about return values or error handling.

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?

Schema description coverage is 0%, so the description must compensate. It provides basic semantic meaning for both parameters (ip=robot address, distance=movement distance in meters), which adds value beyond the bare schema. However, it doesn't specify format constraints (e.g., IP format, distance limits/sign conventions) or provide examples, leaving some ambiguity.

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), but doesn't distinguish it from sibling tools like movel_x or movel_z beyond the axis direction. It's specific about what it does but lacks explicit differentiation from similar movement tools.

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 alternatives like movel_x, movel_z, or other movement commands. The description only explains what the tool does, not when it's appropriate or what prerequisites might be needed (e.g., robot connection status).

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