Skip to main content
Glama
cfrs2005

GS Robot MCP Server

by cfrs2005

upload_robot_map_v1

Upload robot map data to the GS Robot MCP Server using the V1 API to enable navigation and task execution for cleaning robots.

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 the upload_robot_map_v1 tool: validates input, creates GausiumAPIClient, and calls the 'upload_map_v1' endpoint with map_data as JSON.
    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 registration using @mcp.tool() decorator. This is the entry point for the 'upload_robot_map_v1' tool invoked by MCP clients, delegating to GausiumMCP method.
    @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 schema/configuration for 'upload_map_v1' (named 'upload_robot_map_v1'), defining path, method, version used by GausiumAPIClient.call_endpoint.
    '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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Uploads') and mentions a return value, but lacks details on permissions required, rate limits, error handling, or whether the operation is idempotent. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 and front-loaded, with the core purpose stated first, followed by brief sections for args and returns. It avoids unnecessary fluff, though the structure is basic and could be more polished. Every sentence serves a purpose, making it efficient but not exemplary.

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 complexity (a mutation tool with nested objects), lack of annotations, and no output schema, the description is incomplete. It covers the basic action and return hint but misses critical details like behavioral traits, error cases, and full parameter guidance. For a tool that modifies data, this leaves significant gaps for an AI agent to operate safely and effectively.

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 description adds minimal semantics beyond the input schema. It names the parameter ('map_data') and describes it as 'Map data to upload', which is slightly more informative than the schema's 'Map Data' title, but with 0% schema description coverage, it doesn't compensate adequately. The baseline is 3 because the schema provides the structure (object type, required), but the description doesn't elaborate on format or 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 ('Uploads') and resource ('a robot map'), specifying it uses the 'V1 API'. It distinguishes from sibling tools like 'download_robot_map_v1' and 'download_robot_map_v2' by indicating an upload operation, though it doesn't explicitly contrast with other upload-related tools if they exist. The purpose is specific but could be more detailed about what a 'robot map' entails.

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. The description mentions 'V1 API', implying there might be other versions (e.g., V2), but it doesn't specify when to choose V1 over others or list any prerequisites or exclusions. Usage context is minimal, relying solely on the tool name and API version hint.

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