Skip to main content
Glama
cfrs2005

GS Robot MCP Server

by cfrs2005

submit_temp_no_site_task

Submit temporary cleaning tasks for S-line robots using map and area data without requiring site information.

Instructions

Submits a temporary task without site information for S-line robots.

Args:
    task_data: Task data including map and area information.

Returns:
    A dictionary containing the task submission result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_dataYes

Implementation Reference

  • MCP tool handler registered with @mcp.tool(). Delegates to GausiumMCP.submit_temp_no_site_task.
    @mcp.tool()
    async def submit_temp_no_site_task(task_data: dict):
        """Submits a temporary task without site information for S-line robots.
    
        Args:
            task_data: Task data including map and area information.
    
        Returns:
            A dictionary containing the task submission result.
        """
        return await mcp.submit_temp_no_site_task(task_data=task_data)
  • Core implementation in GausiumMCP class. Calls GausiumAPIClient.call_endpoint to submit task data to the 'submit_temp_no_site_task' API endpoint.
    async def submit_temp_no_site_task(
        self,
        task_data: Dict[str, Any]
    ) -> Dict[str, Any]:
        """
        S线无站点临时任务下发。
    
        Args:
            task_data: 任务数据,包含地图、区域等信息
    
        Returns:
            任务下发结果
    
        Raises:
            ValueError: 任务数据无效
            httpx.HTTPStatusError: API调用错误
            httpx.RequestError: 网络问题
        """
        if not task_data:
            raise ValueError("Task data cannot be empty")
    
        async with GausiumAPIClient() as client:
            return await client.call_endpoint(
                'submit_temp_no_site_task',
                json_data=task_data
            )
  • API endpoint schema/definition used by the client, specifying path '/v1alpha1/tasks/temporary/no-site', POST method.
    'submit_temp_no_site_task': APIEndpoint(
        name="submit_temp_no_site_task", 
        path="tasks/temporary/no-site",
        method=HTTPMethod.POST,
        version=APIVersion.V1_ALPHA1,
        description="S线无站点临时任务下发"
  • Usage in S-line no-site task workflow as part of TaskExecutionEngine.execute_s_line_no_site_task.
    task_result = await client.call_endpoint(
        'submit_temp_no_site_task',
        json_data=task_data
    )
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool 'submits' a task, implying a write operation, but doesn't describe what 'temporary' means, whether the submission is synchronous/asynchronous, error handling, or any side effects. The return format is vaguely described as 'a dictionary containing the task submission result' without details.

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 sized with three sentences: purpose, args, and returns. It's front-loaded with the main action, and each sentence serves a clear function without unnecessary elaboration. However, the parameter explanation could be more detailed given the complexity.

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, 1 parameter with 0% schema coverage and nested objects, the description is incomplete. It lacks details on the 'task_data' structure, the meaning of 'temporary', the submission process, and the return value specifics. For a tool that submits tasks, this leaves significant gaps for an agent to use it correctly.

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?

Schema description coverage is 0%, so the description must compensate. It states 'task_data: Task data including map and area information', which adds some meaning beyond the generic schema. However, with 1 parameter and nested objects (true), this is insufficient—it doesn't explain the structure of 'task_data', what 'map and area information' entails, or provide examples.

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 ('submits') and resource ('a temporary task without site information for S-line robots'), making the purpose understandable. It distinguishes from sibling 'submit_temp_site_task' by specifying 'without site information', though it doesn't explicitly differentiate from other task-related tools like 'execute_s_line_no_site_task_workflow'.

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 minimal guidance by specifying 'without site information for S-line robots', which implies usage context but doesn't explicitly state when to use this tool versus alternatives like 'submit_temp_site_task' or 'execute_s_line_no_site_task_workflow'. No exclusions or prerequisites are mentioned.

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/cfrs2005/mcp-gs-robot'

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