Skip to main content
Glama
cfrs2005

GS Robot MCP Server

by cfrs2005

download_robot_map_v2

Download robot maps from the GS Robot MCP Server using the V2 API by specifying a map ID to retrieve navigation data for cleaning robots.

Instructions

Downloads a robot map using V2 API.

Args:
    map_id: The ID of the map to download.

Returns:
    A dictionary containing the map download information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
map_idYes

Implementation Reference

  • Core handler implementation for the download_robot_map_v2 tool. Validates input and uses GausiumAPIClient to call the V2 map download API endpoint.
    async def download_robot_map_v2(self, map_id: str) -> Dict[str, Any]:
        """
        V2地图下载。
    
        Args:
            map_id: 地图ID
    
        Returns:
            地图下载信息
    
        Raises:
            ValueError: map_id为空
            httpx.HTTPStatusError: API调用错误
            httpx.RequestError: 网络问题
        """
        if not map_id:
            raise ValueError("Map ID cannot be empty")
    
        async with GausiumAPIClient() as client:
            return await client.call_endpoint(
                'download_map_v2',
                path_params={'map_id': map_id}
            )
  • MCP tool registration and thin wrapper handler that delegates to the GausiumMCP class method.
    @mcp.tool()
    async def download_robot_map_v2(map_id: str):
        """Downloads a robot map using V2 API.
    
        Args:
            map_id: The ID of the map to download.
    
        Returns:
            A dictionary containing the map download information.
        """
        return await mcp.download_robot_map_v2(map_id=map_id)
  • API endpoint configuration/schema used by the GausiumAPIClient for the download_map_v2 call.
    'download_map_v2': APIEndpoint(
        name="download_robot_map_v2",
        path="map/{map_id}/download",
        method=HTTPMethod.GET,
        version=APIVersion.OPENAPI_V2_ALPHA1,
        description="V2地图下载"
    )
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool downloads a map, implying a read operation, but doesn't disclose behavioral traits like authentication requirements, rate limits, error handling, or whether it's idempotent. The description is minimal and lacks critical operational 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 brief and structured with clear sections for Args and Returns, making it easy to scan. However, the 'Returns' section is vague ('A dictionary containing the map download information'), which adds unnecessary length without adding value.

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, and low schema coverage, the description is incomplete. It lacks details on what the map contains, how to use the returned data, error cases, or integration with sibling tools. For a download operation, this leaves significant gaps for an AI agent.

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?

Schema description coverage is 0%, so the description must compensate. It adds meaning by explaining that 'map_id' is 'The ID of the map to download', which clarifies the parameter's purpose beyond the schema's basic type. However, it doesn't provide details on format, sourcing, or validation, leaving gaps in understanding.

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 action ('Downloads') and resource ('a robot map'), and specifies the API version ('using V2 API'), which distinguishes it from the sibling 'download_robot_map_v1'. However, it doesn't specify what format or content the map includes (e.g., image, data file), leaving some ambiguity.

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 mentions 'V2 API' but doesn't explain when to use this tool versus 'download_robot_map_v1' or other map-related tools like 'list_robot_maps' or 'get_map_subareas'. No guidance is provided on prerequisites, such as needing a valid map ID from another operation.

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