Skip to main content
Glama
nonead

Nonead Universal-Robots MCP Server

by nonead

get_output_int_register

Retrieve the integer register value from a Universal Robot by specifying its IP address and register index (0-23).

Instructions

获取指定IP机器人Int寄存器的值, IP:机器人地址 index:寄存器下标,范围是[0,23]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYes
indexYes

Implementation Reference

  • The MCP tool handler that retrieves the value of an integer output register from a UR robot. It checks connection, calls robotModle_list[ip].OutputIntRegister(index), and returns the result.
    @mcp.tool()
    def get_output_int_register(ip: str, index: int):
        """获取指定IP机器人Int寄存器的值,
        IP:机器人地址
        index:寄存器下标,范围是[0,23]"""
        try:
            if '连接失败' in link_check(ip):
                return return_msg(f"与机器人的连接已断开。")
            logger.info(f"{robotModle_list[ip].OutputIntRegister(index)}")
            return return_msg(f"Int寄存器{index}={robotModle_list[ip].OutputIntRegister(index)}")
        except Exception as e:
            logger.error(f"Int寄存器的值获取失败: {str(e)}")
            return return_msg(f"Int寄存器的值获取失败: {str(e)}")
  • The @mcp.tool() decorator registers 'get_output_int_register' as an MCP tool.
    @mcp.tool()
  • Helper method on RobotModel that returns the output int register value from the data dictionary by constructing the key 'output_int_register_{index}'.
    def OutputIntRegister(self, index):
        address = f"output_int_register_{index}"
        return self.dataDir[address]
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, and the description does not disclose whether the operation is read-only, side effects, error conditions, or other behavioral traits. It simply states it gets a value.

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 very concise (two lines) and front-loaded with the action. However, it could be slightly more structured with clearer separation of parameter explanations.

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?

The tool has no output schema, and the description does not explain the return value format or type. For a simple getter, this is insufficient for an agent to correctly interpret results.

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?

Schema coverage is 0%, so the description partially compensates by explaining the meaning of IP and index, including the index range [0,23]. However, it does not specify IP format or validation details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the action (get the value of an Int register) and the resource (specified IP robot). The name and description differentiate from siblings like get_output_bit_register and get_output_double_register.

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., bit or double register tools). No context on prerequisites or when not to use it.

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/Nonead-Universal-Robots-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server