Skip to main content
Glama
nonead

nUR MCP Server

by nonead

create_collaborative_task

Create multi-robot collaborative tasks by assigning operations to specific robots and defining task dependencies for coordinated industrial automation workflows.

Instructions

创建多机器人协同任务

参数:
- task_name: 任务名称
- robot_assignments: 机器人任务分配,格式为{"robot_id": {"operation": "...", "params": {...}}}
- dependencies: 任务依赖关系列表,格式为[{"from": "task1", "to": "task2"}]

返回:
- 任务创建结果

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_nameYes
robot_assignmentsYes
dependenciesNo

Implementation Reference

  • This is the MCP tool handler function for 'create_collaborative_task'. It is decorated with @mcp.tool(), making it both the registration and the execution logic. The function creates a collaborative task using the AdvancedMultiRobotCoordinator instance.
    @mcp.tool()
    def create_collaborative_task(task_name: str, robot_assignments: dict, dependencies: list = None):
        """
        创建多机器人协同任务
        
        参数:
        - task_name: 任务名称
        - robot_assignments: 机器人任务分配,格式为{"robot_id": {"operation": "...", "params": {...}}}
        - dependencies: 任务依赖关系列表,格式为[{"from": "task1", "to": "task2"}]
        
        返回:
        - 任务创建结果
        """
        try:
            if multi_robot_coordinator is None:
                return return_msg("多机器人协调器未初始化")
            
            # 创建任务
            task_id = multi_robot_coordinator.create_collaboration_task(
                task_name=task_name,
                robot_assignments=robot_assignments,
                dependencies=dependencies
            )
            
            return return_msg(f"协同任务创建成功,任务ID: {task_id}")
        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 states this is a creation operation but doesn't mention permissions needed, whether tasks are persistent, error conditions, or what '任务创建结果' (task creation result) contains. For a tool that creates multi-robot tasks with complex parameters, this is insufficient behavioral 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 well-structured with clear sections for parameters and return value. Each sentence serves a purpose: stating the action, explaining parameters, and mentioning the return. However, the return statement '任务创建结果' is vague and could be more specific about what information is returned.

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 complexity (3 parameters with nested objects, no annotations, no output schema), the description is minimally adequate. It covers the basic purpose and parameter meanings but lacks crucial behavioral context for a creation tool in a multi-robot system. Without annotations or output schema, more detail about permissions, error handling, and result format would be needed for completeness.

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 provides essential semantic information about all three parameters. It explains that 'robot_assignments' maps robot IDs to operations with parameters, and 'dependencies' defines task relationships. This adds significant value beyond the bare schema, though it doesn't detail operation types or dependency constraints.

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 verb '创建' (create) and resource '多机器人协同任务' (multi-robot collaborative task), making the purpose explicit. It distinguishes from siblings like 'execute_collaborative_task' by focusing on creation rather than execution. However, it doesn't fully differentiate from 'setup_multi_robot_coordination' which might be related.

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 on when to use this tool versus alternatives. While it's clear this creates tasks, there's no mention of prerequisites, when to use 'execute_collaborative_task' instead, or what happens after creation. The description lacks context about the workflow or relationship with other tools.

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