Skip to main content
Glama
nonead

nUR MCP Server

by nonead

get_time

Retrieve robot uptime in seconds by providing an IP address to monitor operational duration for Universal Robots industrial systems.

Instructions

根据用户提供的IP,获取指定机器人的开机时长(秒) IP:机器人地址

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYes

Implementation Reference

  • The main handler function for the 'get_time' MCP tool. It is decorated with @mcp.tool(), which registers it and defines its schema from the signature and docstring. The function checks the robot connection via link_check, retrieves the uptime using robotModle_list[ip].RobotTimestamp(), and returns it as a formatted JSON string.
    @mcp.tool()
    def get_time(ip: str) -> str:
        """根据用户提供的IP,获取指定机器人的开机时长(秒)
        IP:机器人地址"""
        try:
            if '连接成功' not in link_check(ip):
                return return_msg(f"与机器人的连接已断开。IP:{ip}")
            logger.info(f"{robotModle_list[ip].RobotTimestamp():.2f}")
            return return_msg(f"{robotModle_list[ip].RobotTimestamp():.2f}")
        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 describes a read operation (获取/get) but doesn't mention whether this requires authentication, has rate limits, returns structured data, or what happens with invalid IPs. The description is functional but lacks important operational context for a tool that presumably queries robot systems.

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 two sentences. The first sentence states the purpose, and the second clarifies the parameter. There's no unnecessary repetition or fluff, though it could be slightly more structured by separating purpose from parameter explanation.

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 the tool's apparent complexity (querying robot boot time), lack of annotations, no output schema, and minimal parameter documentation, the description is incomplete. It doesn't explain what the return value represents (e.g., seconds since boot, formatted string), error conditions, or how this integrates with the broader robot management context suggested by sibling tools.

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?

The description adds minimal parameter semantics beyond the schema. It states 'IP:机器人地址' (IP: robot address), which clarifies that the IP parameter refers to a robot's address, but doesn't specify format (IPv4, hostname), validation rules, or examples. With 0% schema description coverage and only one parameter, this provides basic clarification but doesn't fully compensate for the schema's lack of descriptions.

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: '获取指定机器人的开机时长(秒)' (get the specified robot's boot time in seconds). It specifies both the verb (get) and resource (robot boot time), though it doesn't explicitly differentiate from sibling tools like 'get_actual_joint_current' or 'get_robot_mode' beyond the specific metric being retrieved.

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 usage guidance. It states that an IP address is required ('IP:机器人地址'), but offers no context about when to use this tool versus alternatives like 'get_robot_mode' or 'analyze_robot_data'. There's no mention of prerequisites, error conditions, or typical use cases.

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