Skip to main content
Glama
nonead

Nonead Universal-Robots MCP Server

by nonead

get_safety_mode

Retrieve the current safety mode status of a Universal Robot by providing its IP address to monitor operational safety.

Instructions

获取指定IP机器人的安全模式 IP:机器人地址

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYes

Implementation Reference

  • The handler function for the 'get_safety_mode' tool. Decorated with @mcp.tool(), it checks robot connection, calls DashboardClient.ur_safetymode() to query the safety mode, and returns the result via return_msg().
    @mcp.tool()
    def get_safety_mode(ip: str):
        """获取指定IP机器人的安全模式
        IP:机器人地址"""
        try:
            if '连接失败' in link_check(ip):
                return return_msg(f"与机器人的连接已断开。")
            robot_list[ip].robotConnector.DashboardClient.ur_safetymode()
            result = robot_list[ip].robotConnector.DashboardClient.last_respond
            logger.info(f"IP为{ip}的优傲机器人的安全模式是{result}")
            return return_msg(f"IP为{ip}的优傲机器人的安全模式是{result}")
        except Exception as e:
            logger.error(f"安全模式获取失败: {str(e)}")
            return return_msg(f"安全模式获取失败: {str(e)}")
  • The @mcp.tool() decorator registers get_safety_mode as an MCP tool on the FastMCP server instance named 'mcp'.
    @mcp.tool()
  • Helper utility used by the handler to format return messages as JSON.
    def return_msg(txt: str):
        return json.dumps(txt, indent=2, ensure_ascii=False)
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, authentication needs, or response format. The agent knows it's a read operation but lacks detail about what 'safety mode' constitutes.

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 extremely concise, consisting of a single sentence. While it lacks detail, it is front-loaded with the core purpose. It could be slightly more structured but remains efficient.

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

Completeness3/5

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

For a simple tool with one parameter, the description is minimally adequate. However, it lacks output information and does not explain how safety mode relates to other robot states, making it incomplete for an AI agent to use effectively.

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

Parameters2/5

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

The description restates the parameter 'IP' but adds minimal meaning beyond the input schema. With 0% schema description coverage, the description should clarify the IP format or expected value range, which it does not.

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 retrieves the safety mode of a robot specified by IP. It is specific and distinguishes from sibling tools like 'get_robot_mode' which likely returns the overall robot mode.

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?

There is no guidance on when to use this tool versus alternatives like get_robot_mode or other status tools. No context is provided about prerequisites or scenarios for checking safety mode.

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