Skip to main content
Glama
handsomejustin

Xiaomi smart home MCP server

get_home

Retrieve home details and list all devices in it by providing the home ID.

Instructions

获取家庭详情,包含该家庭下的所有设备列表。

Args:
    home_id: 家庭ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
home_idYes

Implementation Reference

  • MCP tool handler for get_home. Makes an HTTP GET request to /homes/{home_id} via the MCP server, returning home details with all devices.
    @mcp.tool()
    async def get_home(home_id: str) -> dict:
        """获取家庭详情,包含该家庭下的所有设备列表。
    
        Args:
            home_id: 家庭ID
        """
        return await _request("GET", f"/homes/{home_id}")
  • Flask API route handler for GET /homes/<home_id>. Authenticated endpoint that delegates to HomeService.get_home().
    @homes_ns.route("/<home_id>", methods=["GET"])
    @auth_required
    @limiter.limit("60 per minute")
    def get_home(home_id):
        """获取家庭详情
        ---
        tags:
          - 家庭
        security:
          - cookieAuth: []
          - bearerAuth: []
        parameters:
          - in: path
            name: home_id
            type: string
            required: true
        responses:
          200:
            description: 家庭详情
          404:
            description: 家庭未找到
        """
        try:
            home = HomeService.get_home(get_current_user_id(), home_id)
            return success(home)
        except ValueError as e:
            return error(str(e), 404)
        except Exception as e:
            return error(str(e), 500)
  • Service layer method that retrieves home details from the HomeCache database table by user_id and home_id.
    def get_home(user_id: int, home_id: str) -> dict:
        cached = HomeCache.query.filter_by(user_id=user_id, home_id=home_id).first()
        if not cached:
            raise ValueError(f"家庭 {home_id} 未找到")
        return {
            "home_id": cached.home_id,
            "name": cached.name,
            "room_list": cached.room_list,
            "raw_data": cached.raw_data,
        }
  • SQLAlchemy model (HomeCache) that stores cached home data including home_id, name, room_list, and raw_data per user.
    class HomeCache(db.Model):
        __tablename__ = "home_caches"
    
        id = db.Column(db.Integer, primary_key=True, autoincrement=True)
        user_id = db.Column(db.Integer, db.ForeignKey("users.id", ondelete="CASCADE"), nullable=False, index=True)
        home_id = db.Column(db.String(64), nullable=False)
        name = db.Column(db.String(128), nullable=False)
        room_list = db.Column(db.JSON, nullable=True)
        raw_data = db.Column(db.JSON, nullable=True)
        cached_at = db.Column(db.DateTime, default=lambda: datetime.now(timezone.utc))
    
        __table_args__ = (db.UniqueConstraint("user_id", "home_id", name="uk_home_caches_user_home"),)
    
        def __repr__(self):
            return f"<HomeCache {self.name} home_id={self.home_id}>"
  • MCP tool registration via @mcp.tool() decorator. The FastMCP instance 'mcp' is created in the same file.
    @mcp.tool()
    async def get_home(home_id: str) -> dict:
        """获取家庭详情,包含该家庭下的所有设备列表。
    
        Args:
            home_id: 家庭ID
        """
        return await _request("GET", f"/homes/{home_id}")
Behavior1/5

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

No annotations are provided, and the description does not disclose behavioral aspects such as read-only nature, authentication requirements, or whether the operation is destructive. The description carries the full burden but only states functionality.

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 extremely concise: a single sentence with a clear 'Args' section. No wasted words or redundancy.

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 has only one parameter and no output schema, the description covers the basic purpose but lacks details on return structure, error cases, or usage context relative to siblings. Minimally complete.

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?

With 0% schema description coverage, the description adds minimal value by labeling 'home_id' as '家庭ID' (home ID), but this is nearly redundant with the parameter name and does not specify format, constraints, or source of the ID.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it retrieves home details including the list of devices, effectively distinguishing it from siblings like 'list_homes' and 'get_device'.

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 (e.g., 'list_homes' for all homes, 'get_device' for a specific device). No exclusions or context provided.

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/handsomejustin/mijia-control'

If you have feedback or need assistance with the MCP directory API, please join our Discord server