Skip to main content
Glama
nonead

nUR MCP Server

by nonead

disconnect_ur

Disconnect from a Universal Robots collaborative robot by providing its IP address to terminate the connection.

Instructions

根据用户提供的IP,断开与UR机器人的连接 IP:机器人地址

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYes

Implementation Reference

  • The main handler function for the 'disconnect_ur' tool, decorated with @mcp.tool() for registration in FastMCP. It closes the connection to the UR robot identified by the given IP address using robot_list[ip].close(), handling cases where the connection doesn't exist and logging the result.
    @mcp.tool()
    def disconnect_ur(ip: str):
        """根据用户提供的IP,断开与UR机器人的连接
        IP:机器人地址"""
        try:
            if robot_list.get(ip, "unknown") == "unknown":
                return return_msg("连接不存在")
            robot_list[ip].close()
            logger.info(f"连接已断开。IP:{ip}")
            return return_msg("连接已断开。")
        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 states the action is to disconnect but doesn't describe what happens during disconnection (graceful shutdown vs abrupt termination), whether the robot stops operations, if there are safety implications, or what the expected outcome is. For a potentially disruptive operation with zero annotation coverage, this is insufficient.

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 with two sentences that directly address the tool's purpose and parameter. No wasted words or redundant information. However, the second sentence 'IP:机器人地址' is somewhat redundant with the first sentence's mention of IP, slightly reducing efficiency.

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 tool that performs a potentially disruptive network operation with no annotations and no output schema, the description is incomplete. It doesn't explain what 'disconnect' means operationally, what happens to the robot, whether there are safety considerations, or what the tool returns. Given the complexity and lack of structured data, more behavioral context is needed.

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 does identify the single parameter 'ip' as '机器人地址' (robot address), adding semantic meaning beyond the schema's bare 'Ip' title. However, it doesn't provide format details (IPv4, hostname), validation rules, or examples. The description adds basic context but leaves significant gaps.

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 ('断开与UR机器人的连接' - disconnect from UR robot) and the resource (UR robot), specifying it uses an IP address. It distinguishes from sibling tools like 'connect_ur' by being the opposite operation. However, it doesn't specify what 'disconnect' entails operationally beyond the basic action.

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 minimal guidance - it only states to use when you have an IP address. No explicit when-not-to-use scenarios, no mention of prerequisites (e.g., must be connected first), and no comparison to alternatives. The presence of 'connect_ur' as a sibling suggests this is for terminating connections, but this isn't 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