Skip to main content
Glama
nonead

nUR MCP Server

by nonead

send_program_script

Send program scripts to Universal Robots at specified IP addresses to control industrial robots through voice or text commands.

Instructions

发送脚本到指定IP的机器人。 IP:机器人地址 script:脚本内容

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYes
scriptYes

Implementation Reference

  • The handler function for the 'send_program_script' tool, registered via @mcp.tool() decorator. It checks the robot connection, sends the script using RealTimeClient.SendProgram, and returns success or error message.
    @mcp.tool()
    def send_program_script(ip: str, script: str):
        """发送脚本到指定IP的机器人。
        IP:机器人地址
        script:脚本内容"""
        try:
            if '连接失败' in link_check(ip):
                return return_msg(f"与机器人的连接已断开。")
            robot_list[ip].robotConnector.RealTimeClient.SendProgram(script)
            time.sleep(1)
            logger.info(f"发送脚本:{script}")
            return return_msg(f"脚本程序已发送,请确认执行结果。")
        except Exception as e:
            logger.error(f"发送脚本失败: {str(e)}")
            return return_msg(f"发送脚本失败: {str(e)}")
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions sending a script to a robot but doesn't describe what happens after sending (e.g., immediate execution, queuing, validation), potential side effects, error conditions, or authentication requirements. This is inadequate for a tool that likely performs robot control operations.

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 brief and front-loaded with the core purpose. However, the two parameter explanations are somewhat redundant with the schema titles and could be more efficiently integrated into a single cohesive sentence.

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?

For a robot control tool with 2 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the tool returns, error handling, safety considerations, or how it interacts with other robot operations in the sibling toolset, leaving significant gaps for an AI agent.

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

Parameters2/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 but provides only minimal parameter clarification. It mentions 'IP:机器人地址' (IP: robot address) and 'script:脚本内容' (script: script content), which adds basic meaning but lacks format details (e.g., IP format, script language/syntax), constraints, or examples needed for proper usage.

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 action ('发送脚本' - send script) and target resource ('指定IP的机器人' - robot at specified IP), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'execute_collaborative_task' or 'get_programs', which might involve similar robot operations.

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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites, timing considerations, or how this differs from other robot control tools in the sibling list.

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