Skip to main content
Glama
nonead

Nonead Universal-Robots MCP Server

by nonead

send_program_script

Send a URScript program directly to a Universal Robot cobot at a specified IP address for execution.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYes
scriptYes

Implementation Reference

  • The @mcp.tool() decorated function that implements the 'send_program_script' tool. It accepts 'ip' (robot address) and 'script' (URScript content), checks the connection via link_check, sends the script to the robot via RealTimeClient.SendProgram, and returns a success or failure 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)}")
  • The @mcp.tool() decorator on the FastMCP instance 'mcp' registers send_program_script as an MCP tool. This is the registration point.
    @mcp.tool()
    def send_program_script(ip: str, script: str):
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states the action without side effects, idempotency, or execution details. The description does not say whether the script is executed immediately or requires additional steps.

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 very short (two sentences) and front-loaded with the main action. It wastes no words but could be slightly more structured with clearer parameter explanations.

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 or output schema, the description should provide more context. It lacks information about what happens after sending (execution?), required robot state, or any return values. This is insufficient for an agent to use the tool safely.

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?

The input schema has no descriptions (0% coverage). The description adds minimal meaning: 'IP: robot address, script: script content', which is essentially restating the parameter names. No format, constraints, or examples are given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: sending a script to a robot at a specified IP. It uses a specific verb ('send') and resource ('script'), and distinguishes from sibling tools like move commands or data retrieval.

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 on when to use this tool versus alternatives. It does not mention prerequisites (e.g., robot connectivity) or when not to use it. Sibling tools include many other operations, but no comparison is provided.

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/Nonead-Universal-Robots-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server