Skip to main content
Glama
nonead

nUR MCP Server

by nonead

get_actual_robot_current

Retrieve the current electrical load in amperes from a Universal Robot by specifying its IP address to monitor robot performance and operational status.

Instructions

获取指定IP机器人的电流(安培) IP:机器人地址

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYes

Implementation Reference

  • Handler function for the 'get_actual_robot_current' tool. It checks the robot connection via link_check, retrieves the actual robot current using robotModle_list[ip].ActualRobotCurrent(), logs it, and returns the value in a JSON-formatted message. Handles exceptions by logging and returning an error message.
    @mcp.tool()
    def get_actual_robot_current(ip: str):
        """获取指定IP机器人的电流(安培)
        IP:机器人地址"""
        try:
            if '连接失败' in link_check(ip):
                return return_msg(f"与机器人的连接已断开。")
            logger.info(f"{robotModle_list[ip].ActualRobotCurrent()}(安培)")
            return return_msg(f"{robotModle_list[ip].ActualRobotCurrent()}(安培)")
        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 what the tool does but doesn't describe how it behaves: whether it requires authentication, has rate limits, returns real-time vs cached data, error conditions, or response format. For a tool that presumably queries hardware, this lack of behavioral context is significant.

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 short sentences that directly state the purpose and parameter meaning. No wasted words or redundant information. However, it could be slightly more structured by separating purpose from parameter explanation more clearly.

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 complexity of querying robot hardware with no annotations, no output schema, and incomplete parameter documentation, the description is insufficient. It doesn't explain what format the current value returns in, units clarification, error handling, or dependencies on robot connection state. For a tool interacting with physical hardware, more 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?

The description adds minimal semantic context beyond the schema. It clarifies that the 'ip' parameter is '机器人地址' (robot address), which slightly elaborates on the schema's 'Ip' title. However, with 0% schema description coverage and only one parameter, this doesn't fully compensate - it doesn't explain IP format, validation, or examples. The baseline for 0 parameters would be 4, but here we have 1 parameter with incomplete documentation.

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) and the resource '指定IP机器人的电流' (current of specified IP robot), with the unit '安培' (amperes) providing specificity. It distinguishes from siblings like 'get_actual_joint_current' by focusing on overall robot current rather than joint-specific measurements. However, it doesn't explicitly contrast with other current-related tools.

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, nor does it compare with sibling tools like 'get_actual_joint_current' or 'get_actual_robot_voltage'. The agent must infer usage from the tool 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