Skip to main content
Glama
cfrs2005

GS Robot MCP Server

by cfrs2005

get_site_info

Retrieve site information for a GS cleaning robot, including building layouts, floor plans, and map data to support navigation and task planning.

Instructions

Gets site information for a specific robot.

Based on: https://developer.gs-robot.com/zh_CN/Robot%20Task%20Service/Get%20Site%20Info

Args:
    robot_id: The ID of the target robot.

Returns:
    A dictionary containing site information including buildings, floors, and maps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
robot_idYes

Implementation Reference

  • MCP tool registration for 'get_site_info' using @mcp.tool() decorator, with docstring defining input/output schema.
    @mcp.tool()
    async def get_site_info(robot_id: str):
        """Gets site information for a specific robot.
    
        Based on: https://developer.gs-robot.com/zh_CN/Robot%20Task%20Service/Get%20Site%20Info
    
        Args:
            robot_id: The ID of the target robot.
    
        Returns:
            A dictionary containing site information including buildings, floors, and maps.
        """
        return await mcp.get_site_info(robot_id=robot_id)
  • Core handler implementation in GausiumMCP class that invokes the Gausium API client to fetch site information.
    async def get_site_info(self, robot_id: str) -> Dict[str, Any]:
        """
        获取站点信息。
    
        Args:
            robot_id: 机器人ID
    
        Returns:
            站点信息,包括建筑、楼层和地图
    
        Raises:
            ValueError: robot_id为空
            httpx.HTTPStatusError: API调用错误
            httpx.RequestError: 网络问题
        """
        if not robot_id:
            raise ValueError("Robot ID cannot be empty")
    
        async with GausiumAPIClient() as client:
            return await client.call_endpoint(
                'get_site_info',
                path_params={'robot_id': robot_id}
            )
  • API endpoint configuration definition used by GausiumAPIClient for the get_site_info call.
    'get_site_info': APIEndpoint(
        name="get_site_info",
        path="robots/{robot_id}/getSiteInfo", 
        method=HTTPMethod.GET,
        version=APIVersion.OPENAPI_V2_ALPHA1,
        description="获取站点信息"
    ),
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 mentions the return format ('A dictionary containing site information including buildings, floors, and maps'), which adds some context beyond the input schema. However, it lacks details on permissions, rate limits, error conditions, or whether it's a read-only operation, leaving significant gaps for a tool that likely involves data retrieval.

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

Conciseness5/5

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

The description is well-structured and front-loaded, starting with the core purpose, followed by a reference link, and then clear sections for arguments and returns. Every sentence adds value without redundancy, making it efficient and easy to parse.

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 the tool's moderate complexity (single parameter, no output schema, no annotations), the description is partially complete. It covers the purpose and parameter semantics adequately but lacks usage guidelines and full behavioral transparency (e.g., no mention of authentication or error handling). The absence of an output schema means the return value description is helpful but not exhaustive.

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

Parameters4/5

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

The description adds meaningful context for the single parameter 'robot_id' by specifying it as 'The ID of the target robot', which clarifies its purpose beyond the schema's generic 'Robot Id' title. With schema description coverage at 0% and only one parameter, this compensation is effective, though it doesn't detail format constraints (e.g., expected string pattern).

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 with a specific verb ('Gets') and resource ('site information for a specific robot'), distinguishing it from siblings like 'get_robot_status_smart' or 'list_robots'. However, it doesn't explicitly differentiate from 'get_map_subareas' or 'list_robot_maps', which might also involve site-related data, 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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't specify if this should be used instead of 'list_robots' for detailed site data or clarify its role relative to map-related tools like 'get_map_subareas'. The description only states what it does, not when it's appropriate.

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