Skip to main content
Glama
nonead

nUR MCP Server

by nonead

get_output_double_register

Retrieve the current value from a Universal Robots collaborative robot's double register by specifying the robot IP address and register index (0-23).

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYes
indexYes

Implementation Reference

  • The main handler function for the 'get_output_double_register' tool. It retrieves the value of a specified double output register from a UR robot given its IP and register index. The @mcp.tool() decorator registers this function as an MCP tool, with schema inferred from parameters (ip: str, index: int) and docstring.
    @mcp.tool()
    def get_output_double_register(ip: str, index: int):
        """获取指定IP机器人Double寄存器的值,
        IP:机器人地址
        index:寄存器下标,范围是[0,23]"""
        try:
            if '连接失败' in link_check(ip):
                return return_msg(f"与机器人的连接已断开。")
            logger.info(f"Double寄存器{index}={robotModle_list[ip].OutputDoubleRegister(index)}")
            return return_msg(f"{robotModle_list[ip].OutputDoubleRegister(index)}")
        except Exception as e:
            logger.error(f"Double寄存器的值获取失败: {str(e)}")
            return return_msg(f"Double寄存器的值获取失败: {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. The description states this is a read operation ('获取' - get), which implies it's non-destructive, but doesn't explicitly confirm this. It doesn't mention authentication requirements, rate limits, error conditions, or what the return value looks like (e.g., numeric format, units). For a tool with zero 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: one stating the purpose and one explaining parameters. Both sentences earn their place by providing essential information. The structure is front-loaded with the purpose first, followed by parameter details. There's no wasted verbiage or redundancy.

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 (robot control system tool), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what a 'Double register' is, what the returned value represents (e.g., data type, units), or potential error conditions. For a tool that presumably returns numeric data from industrial equipment, this leaves too much unspecified for reliable agent use.

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?

With 0% schema description coverage, the description must compensate for the lack of parameter documentation in the schema. It successfully explains both parameters: 'IP:机器人地址' (IP: robot address) and 'index:寄存器下标,范围是[0,23]' (index: register subscript, range [0, 23]). This adds essential meaning beyond the bare schema, though it doesn't provide examples or format details for the IP parameter.

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机器人Double寄存器的值' (Get the value of a specified IP robot's Double register). It specifies the verb ('获取' - get) and resource ('Double寄存器的值' - Double register value), making the function unambiguous. However, it doesn't differentiate from sibling tools like 'get_output_bit_register' or 'get_output_int_register' beyond mentioning 'Double' specifically.

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_int_register', nor does it explain what makes a 'Double register' different from other register types. The only contextual information is the parameter explanations, which don't constitute usage guidelines.

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