Skip to main content
Glama
cfrs2005

GS Robot MCP Server

by cfrs2005

upload_robot_map_v1

Upload map data to a GS cleaning robot for navigation. Provide map details and receive a record ID for tracking.

Instructions

Uploads a robot map using V1 API.

Args:
    map_data: Map data to upload.

Returns:
    A dictionary containing the upload result with record_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
map_dataYes

Implementation Reference

  • Core implementation of upload_robot_map_v1 - validates input and calls the API endpoint via GausiumAPIClient.call_endpoint with 'upload_map_v1' endpoint name
    async def upload_robot_map_v1(
        self,
        map_data: Dict[str, Any]
    ) -> Dict[str, Any]:
        """
        V1地图上传。
    
        Args:
            map_data: 地图数据
    
        Returns:
            上传结果,包含record_id
    
        Raises:
            ValueError: 地图数据为空
            httpx.HTTPStatusError: API调用错误
            httpx.RequestError: 网络问题
        """
        if not map_data:
            raise ValueError("Map data cannot be empty")
    
        async with GausiumAPIClient() as client:
            return await client.call_endpoint(
                'upload_map_v1',
                json_data=map_data
            )
  • MCP tool decorator registration of upload_robot_map_v1 - the entry point exposed via @mcp.tool(), delegates to mcp.upload_robot_map_v1
    @mcp.tool()
    async def upload_robot_map_v1(map_data: dict):
        """Uploads a robot map using V1 API.
    
        Args:
            map_data: Map data to upload.
    
        Returns:
            A dictionary containing the upload result with record_id.
        """
        return await mcp.upload_robot_map_v1(map_data=map_data)
  • API endpoint definition for 'upload_map_v1' - maps to the 'map/upload' path with POST method under OPENAPI_V1
    'upload_map_v1': APIEndpoint(
        name="upload_robot_map_v1",
        path="map/upload",
        method=HTTPMethod.POST,
        version=APIVersion.OPENAPI_V1,
        description="V1地图上传"
    ),
Behavior2/5

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

With no annotations, the description must convey behavioral traits. It only states 'uploads', but does not disclose side effects (e.g., overwriting), idempotency, error conditions, or required permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and includes the args/returns section, but the structure is minimal and lacks detail. It is concise but under-specified.

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 the tool's mutation nature and lack of output schema, the description is incomplete. It omits error handling, return value details beyond 'record_id', and any context about map data requirements.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds minimal value over the schema: 'Map data to upload' does not clarify format, structure, or constraints. The schema has 0% description coverage, and the description fails to compensate.

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 uploads a robot map via V1 API, which distinguishes it from sibling tools like download_robot_map_v1 or list_robot_maps. However, it does not elaborate on the V1 API specifics.

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, prerequisites, or alternatives. It only defines the action without contextual usage advice.

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