Skip to main content
Glama
nonead

nUR MCP Server

by nonead

get_safety_mode

Retrieve the safety mode status of a Universal Robots collaborative robot by providing its IP address to monitor operational safety settings.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYes

Implementation Reference

  • The main handler function for the 'get_safety_mode' tool. It checks the robot connection, sends the 'ur_safetymode()' command via DashboardClient, and returns the safety mode result. Registered as an MCP tool via @mcp.tool() decorator.
    @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)}")
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 retrieves safety mode, implying a read-only operation, but doesn't disclose behavioral traits like whether it requires authentication, has rate limits, returns real-time or cached data, or what happens if the IP is invalid. For a tool with zero annotation coverage, this is inadequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with two short sentences that directly state the purpose and parameter. There is no fluff or redundancy, and it's front-loaded with the core functionality. Every word earns its place.

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 parameter semantics coverage, the description is incomplete. It doesn't explain what safety mode entails, possible return values, error conditions, or dependencies. For a tool in a robotics context with many siblings, more context is needed for effective use.

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?

Schema description coverage is 0%, so the description must compensate. It mentions 'IP:机器人地址' (IP: robot address), which adds meaning by clarifying the IP parameter refers to a robot's address. However, it doesn't explain format (e.g., IPv4, hostname), examples, or constraints, leaving significant gaps for a required parameter.

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 verb '获取' (get/retrieve) and the resource '安全模式' (safety mode) for a specific IP robot. It distinguishes itself from siblings like get_robot_mode or get_robot_model by focusing on safety mode specifically. However, it doesn't explicitly differentiate from all possible siblings, keeping it at 4 instead of 5.

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. It doesn't mention prerequisites like needing a connected robot or compare it to similar tools like get_robot_mode. The agent must infer usage from the name and description alone.

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