Skip to main content
Glama
nonead

nUR MCP Server

by nonead

get_robot_mode

Retrieve the operational status of a Universal Robots collaborative robot by providing its IP address to monitor or verify its current working mode.

Instructions

获取指定IP机器人的运行状态 IP:机器人地址

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYes

Implementation Reference

  • The main handler function for the MCP tool 'get_robot_mode'. It checks the robot connection, calls ur_robotmode() on the DashboardClient to get the robot mode, logs the result, and returns a formatted message. The @mcp.tool() decorator registers this function as an MCP tool.
    @mcp.tool()
    def get_robot_mode(ip: str):
        """获取指定IP机器人的运行状态
        IP:机器人地址"""
        try:
            if '连接失败' in link_check(ip):
                return return_msg(f"与机器人的连接已断开。")
            robot_list[ip].robotConnector.DashboardClient.ur_robotmode()
            logger.info(f"IP为{ip}的优傲机器人的运行状态为: {robot_list[ip].robotConnector.DashboardClient.last_respond}")
            return return_msg(
                f"IP为{ip}的优傲机器人的运行状态为: {robot_list[ip].robotConnector.DashboardClient.last_respond}")
        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. While it indicates this is a read operation ('获取' - get), it doesn't describe what the return value looks like, whether it requires authentication, any rate limits, error conditions, or what specific status information is returned. The description is minimal and leaves critical behavioral aspects unspecified.

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

Conciseness3/5

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

The description is concise with two short sentences, but it's under-specified rather than efficiently informative. The first sentence states the purpose, the second clarifies the parameter, but both are minimal without providing necessary context. While not verbose, it lacks the completeness that would justify higher scores.

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 with no annotations, no output schema, and minimal parameter documentation, the description is incomplete. It doesn't explain what '运行状态' (operating status) encompasses, what format the response takes, or how this differs from other status-retrieval tools. Given the complexity implied by the sibling tools (robot control and monitoring), 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?

The description adds minimal parameter semantics beyond the schema. It states 'IP:机器人地址' (IP: robot address), which clarifies that the 'ip' parameter should be a robot's address, but with 0% schema description coverage and only one parameter, this is insufficient compensation. It doesn't specify the expected format (IPv4, hostname, etc.) or provide examples.

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机器人的运行状态' (Get the operating status of a specified IP robot). It uses a specific verb ('获取' - get) and resource ('运行状态' - operating status), but doesn't distinguish from siblings like 'get_safety_mode' or 'get_program_state' which also retrieve status information about robots.

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 what '运行状态' (operating status) specifically means compared to other status-related tools like 'get_safety_mode' or 'get_program_state', nor does it indicate any prerequisites or exclusions for its use.

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