Skip to main content
Glama
nonead

nUR MCP Server

by nonead

get_actual_joint_current

Retrieve real-time current measurements in amperes for each joint of a Universal Robot at a specified IP address. Use this tool to monitor joint performance and detect potential issues during operation.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYes

Implementation Reference

  • Handler function for the 'get_actual_joint_current' tool, decorated with @mcp.tool() for registration. Retrieves joint currents from the robot model, though it incorrectly calls ActualJointVoltage() instead of ActualJointCurrent(). Uses helpers like link_check and return_msg.
    @mcp.tool()
    def get_actual_joint_current(ip: str):
        """获取指定IP机器人各关节的电流(安培)
        IP:机器人地址"""
        try:
            if '连接失败' in link_check(ip):
                return return_msg(f"与机器人的连接已断开。")
            logger.info(f"{robotModle_list[ip].ActualJointVoltage()}(安培)")
            return return_msg(f"{robotModle_list[ip].ActualJointVoltage()}(安培)")
        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 the full burden. It mentions retrieving current in amperes for joints of a robot at a specified IP, but lacks details on permissions, rate limits, error handling, or whether this is a read-only operation. This is insufficient for a tool with no annotation coverage.

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 concise with two short sentences that directly state the tool's purpose and parameter meaning. It is front-loaded with the main action, though it could be slightly more structured (e.g., separating usage notes). No wasted words, but room for improvement in clarity.

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 schema coverage, the description is incomplete. It does not explain return values (e.g., format of current data), error conditions, or behavioral traits like safety or performance. For a tool in a robotics context with many siblings, this leaves significant gaps.

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 semantics: it clarifies that the 'ip' parameter is the robot address. With 0% schema description coverage and only one parameter, this provides some value beyond the schema, but it's basic. The baseline is 3 due to low parameter complexity, though more detail (e.g., IP format) would improve it.

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 '指定IP机器人各关节的电流' (current of each joint for a specified IP robot), making the purpose specific. However, it does not explicitly differentiate from sibling tools like 'get_actual_joint_voltage' or 'get_actual_robot_current', which reduces clarity in a crowded toolset.

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 (e.g., 'get_actual_joint_voltage' for voltage or 'get_actual_robot_current' for overall robot current). It only states what the tool does, leaving the agent to infer usage from context without explicit instructions.

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