Skip to main content
Glama
nonead

nUR MCP Server

by nonead

get_output_int_register

Retrieve integer register values from Universal Robots by specifying the robot IP address and register index (0-23) for industrial automation control.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYes
indexYes

Implementation Reference

  • The handler function decorated with @mcp.tool(), which registers and implements the get_output_int_register tool. It checks the robot connection, retrieves the integer register value using OutputIntRegister(index), logs it, and returns the result in JSON format.
    @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)}")
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 of behavioral disclosure. It states this is a read operation ('获取' - get), but doesn't mention potential side effects, authentication requirements, rate limits, error conditions, or what the return value looks like. For a tool that accesses hardware registers with no annotation coverage, this leaves significant behavioral gaps.

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 that directly address the tool's purpose and parameters. Each sentence serves a clear purpose: the first states what the tool does, the second explains the parameters. There's no unnecessary information or repetition.

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 accessing hardware registers, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what an 'Int register' is in this context, what format the returned value will have, potential error conditions, or prerequisites like needing an active connection. For a tool that likely interfaces with industrial robots, more context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds crucial semantic information beyond the schema. The schema has 0% description coverage with only generic titles ('Ip', 'Index'), while the description explains: 'IP:机器人地址' (IP: robot address) and 'index:寄存器下标,范围是[0,23]' (index: register subscript, range [0, 23]). This provides essential context about parameter meanings and constraints that the schema lacks.

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机器人Int寄存器的值' (Get the value of a specified IP robot's Int register). It specifies the verb ('获取' - get) and resource ('Int寄存器的值' - Int register value), making the function unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_output_bit_register' or 'get_output_double_register', which appear to access different register types.

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 sibling tools like 'get_output_bit_register' or 'get_output_double_register' that likely access different register types, nor does it explain the context for choosing this specific register type. Usage is implied by the parameter descriptions but not explicitly stated.

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