Skip to main content
Glama
aldilaff
by aldilaff

wyze_get_scale_info

Retrieve detailed information about a specific Wyze smart scale by providing its MAC address to access device data and health metrics.

Instructions

Get detailed information about a specific Wyze scale

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_macYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'wyze_get_scale_info' tool. It uses the Wyze SDK to fetch detailed scale information including family members by device MAC address. The @mcp.tool() decorator automatically registers it with the MCP server.
    @mcp.tool()
    def wyze_get_scale_info(device_mac: str) -> Dict[str, Any]:
        """Get detailed information about a specific Wyze scale"""
        try:
            client = get_wyze_client()
            scale = client.scales.info(device_mac=device_mac)
            
            if scale is None:
                return {"status": "error", "message": f"Scale with MAC {device_mac} not found"}
            
            scale_info = {
                "mac": str(scale.mac) if scale.mac else "Unknown",
                "nickname": str(scale.nickname) if scale.nickname else "Unknown",
                "product_model": str(getattr(scale, 'product_model', 'Unknown')) if getattr(scale, 'product_model', 'Unknown') else "Unknown",
                "product_type": str(getattr(scale, 'product_type', 'Scale')) if getattr(scale, 'product_type', 'Scale') else "Scale",
                "is_online": bool(getattr(scale, 'is_online', True)),
                "firmware_ver": str(getattr(scale, 'firmware_ver', 'N/A')),
            }
            
            # Add family members if available
            if hasattr(scale, 'family_members') and scale.family_members:
                family_members = []
                for member in scale.family_members:
                    member_info = {
                        "id": str(member.get("id", "Unknown")),
                        "nickname": str(member.get("nickname", "Unknown")),
                        "height": float(member.get("height")) if member.get("height") is not None else None,
                        "goal_weight": float(member.get("goal_weight")) if member.get("goal_weight") is not None else None,
                    }
                    family_members.append(member_info)
                scale_info["family_members"] = family_members
            
            return {"status": "success", "scale": scale_info}
        except WyzeClientConfigurationError as e:
            return {"status": "error", "message": f"Configuration error: {str(e)}"}
        except WyzeRequestError as e:
            return {"status": "error", "message": f"API error: {str(e)}"}
        except Exception as e:
            return {"status": "error", "message": f"Unexpected error: {str(e)}"}
  • Helper function to get or initialize the global Wyze client instance, used by wyze_get_scale_info and other tools.
    def get_wyze_client() -> Client:
        """Get or create Wyze client instance with auto-login if credentials available"""
        global _wyze_client
        
        if _wyze_client is None:
            # Get credentials from environment
            email = os.getenv("WYZE_EMAIL")
            password = os.getenv("WYZE_PASSWORD")
            key_id = os.getenv("WYZE_KEY_ID")
            api_key = os.getenv("WYZE_API_KEY")
            
            if not all([email, password, key_id, api_key]):
                raise WyzeClientConfigurationError(
                    "Missing required environment variables: WYZE_EMAIL, WYZE_PASSWORD, WYZE_KEY_ID, WYZE_API_KEY"
                )
            
            _wyze_client = Client(
                email=email,
                password=password,
                key_id=key_id,
                api_key=api_key
            )
        
        return _wyze_client
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks behavioral details. It doesn't disclose whether this is a read-only operation, requires specific permissions, involves network calls or rate limits, or what 'detailed information' entails (e.g., device specs, settings, or state). The phrase 'Get' implies a safe read, but this isn't explicitly confirmed.

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 a single, clear sentence with no wasted words, efficiently stating the tool's purpose. It's appropriately sized for a simple tool and front-loaded with the key action and resource.

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 1 parameter with no schema descriptions, an output schema exists (which should cover return values), and no annotations, the description is minimally adequate but incomplete. It states what the tool does but lacks usage context, behavioral details, and parameter guidance, making it functional but not fully helpful for an agent.

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 schema has 1 parameter with 0% description coverage, so the description must compensate but adds no parameter-specific information. It mentions 'a specific Wyze scale', which implicitly relates to the 'device_mac' parameter, but doesn't explain format (e.g., MAC address structure), sourcing (e.g., from 'wyze_get_scales'), or validation. Baseline 3 is given as the description doesn't fully address the coverage 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 verb 'Get' and the resource 'detailed information about a specific Wyze scale', making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'wyze_get_scales' (which likely lists scales) or 'wyze_get_scale_records' (which might retrieve measurement data), leaving some ambiguity about scope.

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 prerequisites (e.g., needing authentication via 'wyze_login'), compare to siblings like 'wyze_get_scales' for listing devices or 'wyze_device_info' for general device details, or specify contexts where detailed scale info is needed over basic status.

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/aldilaff/mcp-wyze-server'

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