Skip to main content
Glama
cfrs2005

GS Robot MCP Server

by cfrs2005

get_robot_capabilities

Retrieve supported API endpoints and functionality for a specific GS cleaning robot using its serial number to understand available control operations.

Instructions

获取机器人支持的API能力。

显示该机器人支持哪些API端点和功能。

Args:
    serial_number: 机器人序列号
    
Returns:
    机器人能力信息字典

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serial_numberYes

Implementation Reference

  • Registration and thin handler for the 'get_robot_capabilities' tool using @mcp.tool() decorator. Delegates to router.get_capabilities()
    @mcp.tool()
    async def get_robot_capabilities(serial_number: str):
        """获取机器人支持的API能力。
        
        显示该机器人支持哪些API端点和功能。
        
        Args:
            serial_number: 机器人序列号
            
        Returns:
            机器人能力信息字典
        """
        return await router.get_capabilities(serial_number)
  • Core implementation of get_robot_capabilities logic in RobotAPIRouter class. Determines robot series from serial number prefix and returns supported API capabilities based on M-line or S-line classification.
    async def get_capabilities(self, serial_number: str) -> Dict[str, Any]:
        """获取机器人支持的API能力。"""
        # 基于序列号前缀判断机器人系列
        detected_series = self._determine_robot_series_from_sn(serial_number)
        
        capabilities = {
            "basic_status": True,
            "command_control": True,
            "task_reports": True,
            "maps": True,
            "site_info": False,
            "advanced_tasks": False
        }
        
        if self.is_s_line_robot(detected_series):
            capabilities.update({
                "site_info": True,
                "advanced_tasks": True,
                "v2_status": True,
                "v1_status": False
            })
            robot_series = "S-line"
        elif self.is_m_line_robot(detected_series):
            capabilities.update({
                "v1_status": True,
                "v2_status": False,
                "command_control": True
            })
            robot_series = "M-line"
        else:
            # 未知前缀默认使用V1 API
            capabilities.update({
                "v1_status": True,
                "v2_status": False,
                "command_control": True
            })
            robot_series = "Unknown (Default V1)"
        
        return {
            "serial_number": serial_number,
            "robot_series": robot_series,
            "detected_series": detected_series,
            "prefix": serial_number[:5] if len(serial_number) >= 5 else serial_number,
            "capabilities": capabilities
        }
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. While it mentions the tool returns '机器人能力信息字典' (robot capability information dictionary), it doesn't describe what this dictionary contains, whether the operation has side effects, authentication requirements, rate limits, or error conditions. For a tool with no annotation coverage, this leaves significant behavioral questions unanswered.

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 concise with three sentences that each serve a purpose: stating the tool's purpose, elaborating on what it shows, and documenting parameters and returns. It's front-loaded with the main purpose first. While efficient, the Chinese-only text might limit accessibility in multilingual contexts, but this doesn't significantly impact conciseness.

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 (robot capability querying), lack of annotations, 0% schema description coverage, and no output schema, the description is incomplete. It doesn't explain what specific capabilities might be returned, how to interpret the results, or provide examples of the returned dictionary structure. For a tool that presumably returns structured data about robot capabilities, more context is needed for effective use.

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 includes an 'Args' section that documents the single parameter 'serial_number' with a brief explanation. However, with 0% schema description coverage and no output schema, the description doesn't fully compensate. It doesn't explain what format the serial number should be in, provide examples, or describe what happens if an invalid serial number is provided. The parameter documentation is minimal but present.

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: '获取机器人支持的API能力' (Get robot-supported API capabilities) and '显示该机器人支持哪些API端点和功能' (Show which API endpoints and functions this robot supports). It specifies the verb ('获取' - get) and resource ('机器人支持的API能力' - robot API capabilities). However, it doesn't explicitly distinguish this from sibling tools like 'get_robot_status_smart' or 'get_robot_command', which reduces clarity about when to use this specific tool.

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. With sibling tools like 'get_robot_status_smart', 'get_robot_command', and 'list_robots', there's no indication of whether this tool should be used before invoking other robot-related operations, or if it's complementary to those tools. The description only states what the tool does, not when it's appropriate to use it.

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