Skip to main content
Glama
nonead

nUR MCP Server

by nonead
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_serial_number

Retrieve the serial number of a Universal Robots collaborative robot by providing its IP address. This tool enables identification and verification of industrial robots within the nUR MCP Server system.

Instructions

获取指定IP机器人的序列号 IP：机器人地址

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYes

Implementation Reference

  • src/nonead_universal_robots_mcp/server.py:230-244 (handler)
    The MCP tool handler function for 'get_serial_number'. It checks the robot connection via link_check, sends the 'ur_serial_number' command to the robot's DashboardClient, logs and returns the serial number from the response.
    @mcp.tool()
def get_serial_number(ip: str):
    """获取指定IP机器人的序列号
    IP：机器人地址"""
    try:
        if '连接失败' in link_check(ip):
            return return_msg(f"与机器人的连接已断开。")
        robot_list[ip].robotConnector.DashboardClient.ur_serial_number()
        logger.info(f"IP为{ip}的优傲机器人的序列号为： {robot_list[ip].robotConnector.DashboardClient.last_respond}")
        return return_msg(
            f"IP为{ip}的优傲机器人的序列号为： {robot_list[ip].robotConnector.DashboardClient.last_respond}")
    except Exception as e:
        logger.error(f"获取序列号失败: {str(e)}")
        return return_msg(f"获取序列号失败: {str(e)}")

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states what the tool does but doesn't disclose behavioral traits like whether this is a read-only operation, if it requires authentication, potential rate limits, error conditions, or what format the serial number is returned in. The description is minimal and lacks operational context.

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 short sentences that directly state the tool's purpose and parameter. There's no wasted text, though it could be slightly more informative. The structure is front-loaded with the main purpose stated first.

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 0% schema description coverage for a tool that retrieves data from robots, the description is incomplete. It doesn't explain what the return value looks like, potential errors, authentication requirements, or how this differs from other robot data retrieval tools. For a tool interacting with physical hardware, more context is needed.

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 description coverage is 0%, so the description must compensate. It mentions the 'ip' parameter ('IP：机器人地址' - IP: robot address), which adds meaning by clarifying this refers to a robot's IP address. However, it doesn't provide format details (IPv4, hostname), validation rules, or examples. With 1 parameter and minimal schema documentation, this provides basic but insufficient compensation.

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机器人的序列号' (Get the serial number of a specified IP robot). It uses a specific verb ('获取' - get) and resource ('序列号' - serial number), but doesn't explicitly differentiate from sibling tools that also retrieve robot data. The description is clear but lacks sibling differentiation.

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 any prerequisites, constraints, or compare it to similar sibling tools like 'get_robot_model' or 'get_ur_software_version'. The agent must infer usage from the tool name alone.

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