Skip to main content
Glama
nonead

nUR MCP Server

by nonead

draw_circle

Control industrial robots to draw circles by specifying center coordinates, radius, and orientation plane. Use this tool to program circular paths for robotic applications with Universal Robots.

Instructions

命令指定IP的机器人,给定圆心位置和半径,在水平或竖直方向画一个圆 center:圆心的TCP位置 r:半径(米) coordinate:圆所在的平面。z:圆形所在的平面与基座所在平面垂直,其它:圆形所在的平面与基座所在平面平行。默认值:z。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYes
centerYes
rYes
coordinateNoz

Implementation Reference

  • The handler function for the 'draw_circle' MCP tool. It calculates four waypoints around the given center and radius in the specified plane (z or other), generates a URScript program using movep and two movec commands to trace a circle, logs the script, sends it to the robot via RealTimeClient, and returns a success message or error.
    @mcp.tool()
    def draw_circle(ip: str, center: list, r: float, coordinate="z"):
        """命令指定IP的机器人,给定圆心位置和半径,在水平或竖直方向画一个圆
            center:圆心的TCP位置
            r:半径(米)
            coordinate:圆所在的平面。z:圆形所在的平面与基座所在平面垂直,其它:圆形所在的平面与基座所在平面平行。默认值:z。"""
        try:
            if '连接失败' in link_check(ip):
                return return_msg(f"与机器人的连接已断开。")
            wp_1 = [center[0], center[1], center[2], center[3], center[4], center[5]]
            wp_2 = [center[0], center[1], center[2], center[3], center[4], center[5]]
            wp_3 = [center[0], center[1], center[2], center[3], center[4], center[5]]
            wp_4 = [center[0], center[1], center[2], center[3], center[4], center[5]]
            cmd = ''
            if coordinate.lower() == "z":
                wp_1[2] = wp_1[2] + r
    
                wp_2[1] = wp_2[1] + r
    
                wp_3[2] = wp_3[2] - r
    
                wp_4[1] = wp_4[1] - r
            else:
                wp_1[0] = wp_1[0] - r
    
                wp_2[1] = wp_2[1] + r
    
                wp_3[0] = wp_3[0] + r
    
                wp_4[1] = wp_4[1] - r
    
            cmd = (
                f"def my_program():\n"
                f"  movep(p{str(wp_1)}, a=1, v=0.25, r=0.025)\n"
                f"  movec(p{str(wp_2)}, p{str(wp_3)}, a=1, v=0.25, r=0.025, mode=0)\n"
                f"  movec(p{str(wp_4)}, p{str(wp_1)}, a=1, v=0.25, r=0.025, mode=0)\nend\nmy_program()")
            logger.info(f"draw_circle 发送脚本:{cmd}")
            robot_list[ip].robotConnector.RealTimeClient.SendProgram(cmd)
            time.sleep(1)
            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 mentions the action (drawing a circle) but lacks critical behavioral details: whether this is a safe operation, if it requires specific robot modes, potential safety risks, execution time, or what happens on failure. For a robot control tool with zero annotation coverage, this is a significant gap in transparency.

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 concise with three sentences that directly explain the tool's function and parameters. It's front-loaded with the main purpose, though the parameter explanations could be slightly better structured. No wasted words, but minor formatting issues exist in the original text.

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 this is a robot control tool with 4 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't cover execution behavior, error conditions, safety considerations, or what constitutes successful completion. For a tool that presumably moves physical hardware, this level of documentation is inadequate.

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 explains the meaning of 'center' (圆心位置/TCP position), 'r' (半径/radius in meters), and 'coordinate' (平面/plane orientation with default 'z'). However, it doesn't clarify 'ip' parameter or provide units/format for 'center' array. The description adds value for 3 of 4 parameters but leaves one undocumented.

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 tool's purpose: '命令指定IP的机器人,给定圆心位置和半径,在水平或竖直方向画一个圆' (Command a robot at a specified IP, given center position and radius, to draw a circle in horizontal or vertical direction). It specifies the verb (draw), resource (circle), and distinguishes from siblings like draw_rectangle and draw_square by focusing on circles. However, it doesn't explicitly differentiate from other drawing tools beyond mentioning the shape.

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?

The description provides no guidance on when to use this tool versus alternatives like draw_rectangle or draw_square, nor does it mention prerequisites such as needing a connected robot or appropriate robot state. It only describes what the tool does, not when it should be selected over other tools in the sibling list.

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