Skip to main content
Glama
nonead

nUR MCP Server

by nonead

get_output_bit_register

Retrieve Boolean register values from Universal Robots by specifying the robot IP address and register index to monitor or control robot output states.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYes
indexYes

Implementation Reference

  • The main handler function for the 'get_output_bit_register' MCP tool. It connects to the UR robot via IP, checks connection, retrieves the output bit register array, and returns the value at the specified index. The @mcp.tool() decorator registers it as a tool.
    @mcp.tool()
    def get_output_bit_register(ip: str, index: int):
        """获取指定IP机器人Bool寄存器的值,
        IP:机器人地址
        index:寄存器下标,范围是[0,23]"""
        try:
            if '连接失败' in link_check(ip):
                return return_msg(f"与机器人的连接已断开。")
            bits = robotModle_list[ip].OutputBitRegister()
            logger.info(f"Bool寄存器{index}={bits[index]}")
            return return_msg(f"{bits[index]}")
        except Exception as e:
            logger.error(f"Bool寄存器的值获取失败: {str(e)}")
            return return_msg(f"Bool寄存器的值获取失败: {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 the tool reads a Bool register value, implying it's a read-only operation, but doesn't clarify permissions, rate limits, error handling, or response format. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior and constraints.

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 and front-loaded, with the main purpose stated first followed by parameter explanations. It uses minimal sentences (effectively two) with no wasted words, making it easy to parse. However, the structure could be slightly improved by separating purpose and parameters more clearly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (2 parameters, no annotations, no output schema), the description is partially complete. It covers the purpose and parameter semantics adequately but lacks usage guidelines, behavioral details (e.g., response format, errors), and differentiation from siblings. For a read operation with simple parameters, this is minimally viable but has clear gaps.

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 meaningful semantics for both parameters: 'IP:机器人地址' (IP: robot address) and 'index:寄存器下标,范围是[0,23]' (index: register subscript, range [0, 23]). With schema description coverage at 0%, this compensates well by explaining what each parameter represents and providing a critical constraint (the index range), though it doesn't cover all potential details like IP format.

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机器人Bool寄存器的值' (Get the value of a specified IP robot's Bool register). It specifies the verb ('获取' - get) and resource ('Bool寄存器' - Bool register), making the action clear. However, it doesn't explicitly differentiate from sibling tools like 'get_output_double_register' or 'get_output_int_register' beyond the register type, which prevents a perfect score.

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_double_register' or 'get_output_int_register', nor does it specify use cases, prerequisites, or exclusions. The only context is implicit from the tool name and description, which is insufficient for effective tool selection.

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