Skip to main content
Glama
cfrs2005

GS Robot MCP Server

by cfrs2005

download_robot_map_v1

Download robot maps from the GS Robot MCP Server using the V1 API. Provide a map ID to retrieve map data for robot navigation and monitoring.

Instructions

Downloads a robot map using V1 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 that validates input and calls the V1 map download API endpoint via GausiumAPIClient.
    async def download_robot_map_v1(self, map_id: str) -> Dict[str, Any]:
        """
        V1获取地图下载。
    
        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_v1',
                path_params={'map_id': map_id}
            )
  • MCP tool registration with @mcp.tool() decorator, providing the entry point that delegates to the GausiumMCP instance.
    @mcp.tool()
    async def download_robot_map_v1(map_id: str):
        """Downloads a robot map using V1 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_v1(map_id=map_id)
  • API endpoint configuration defining the path, method, version, and description for the download_robot_map_v1 tool.
    'download_map_v1': APIEndpoint(
        name="download_robot_map_v1",
        path="map/{map_id}/download",
        method=HTTPMethod.GET,
        version=APIVersion.OPENAPI_V1,
        description="V1获取地图下载"
    ),
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 states the action ('Downloads') but lacks details on permissions, rate limits, file formats, or error handling. The return value description ('A dictionary containing the map download information') is vague and doesn't specify content like URLs or metadata. This leaves significant gaps for a download operation.

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. The Args and Returns sections are structured but could be more efficient; for example, 'Returns' could be integrated into the main sentence. Overall, it's concise with little waste.

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 of a download operation, no annotations, and no output schema, the description is incomplete. It lacks details on authentication, file handling, error cases, and the structure of the return dictionary. For a tool that interacts with robot maps, more context is needed to ensure correct usage.

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 explains 'map_id: The ID of the map to download,' which clarifies the parameter's purpose, but with 0% schema description coverage and only one parameter, this is adequate. However, it doesn't provide format examples (e.g., UUID) or validation rules, so it doesn't fully compensate for the schema gap.

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's purpose: 'Downloads a robot map using V1 API.' It specifies the verb ('Downloads') and resource ('robot map'), and distinguishes it from the sibling 'download_robot_map_v2' by mentioning 'V1 API'. However, it doesn't explicitly differentiate from other map-related tools like 'list_robot_maps' or 'upload_robot_map_v1', which keeps it from a perfect score.

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 versus alternatives. It doesn't mention when to choose V1 over V2 (e.g., for compatibility), nor does it reference other map-related tools like 'list_robot_maps' for selection or 'upload_robot_map_v1' for opposite operations. Usage is implied only by the tool name and API version.

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