Skip to main content
Glama
cfrs2005

GS Robot MCP Server

by cfrs2005

download_robot_map_v2

Download a robot map by providing its map ID. Retrieves map data using the V2 API for use in navigation and task planning.

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

  • The core handler method `download_robot_map_v2` on the GausiumMCP class that calls the API endpoint 'download_map_v2' via GausiumAPIClient. It validates map_id and delegates to the API client.
    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}
            )
  • The MCP tool registration via `@mcp.tool()` decorator on the `download_robot_map_v2` function. This is the entry point that exposes the tool externally, delegating to `mcp.download_robot_map_v2()`.
    @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)
  • The API endpoint definition for `download_map_v2`, which maps to path `map/{map_id}/download` with method GET and version OPENAPI_V2_ALPHA1. This defines the endpoint configuration used by the API client.
    '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 must bear the burden. It only mentions 'downloads' and 'returns a dictionary' without detailing side effects, permissions, or response structure.

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 but includes unnecessary formatting like 'Args:' and 'Returns:' for a single parameter. It could be more concise without losing clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given simple tool (one parameter), the description adequately states purpose and basic return type, but lacks detail on output format or behavioral context. It meets minimum viability but has gaps.

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?

The only parameter map_id is described as 'The ID of the map to download,' which adds no meaning beyond its schema title. With 0% schema description coverage, the description fails to compensate for missing parameter context.

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 'Downloads a robot map using V2 API,' specifying the verb and resource. It distinguishes from siblings like download_robot_map_v1 by version, though it doesn't elaborate on differences.

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 on when to use this tool versus alternatives such as download_robot_map_v1 or upload_robot_map_v1. It lacks context about prerequisites or scenarios.

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