Skip to main content
Glama
thinq-connect

ThinQ Connect MCP Server

Official

get_device_list

Retrieve all devices connected to the ThinQ Connect platform, returning a list with device information.

Instructions

Retrieves a list of all devices connected to the ThinQ Connect platform Args: None

Returns:
    String containing connected device list information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `@mcp.tool` decorator registers 'get_device_list' as an MCP tool. The async function delegates to `tools.get_device_list(thinq_api=thinq_api)`.
    @mcp.tool(
        description="""Retrieves a list of all devices connected to the ThinQ Connect platform
        Args:
            None
    
        Returns:
            String containing connected device list information
        """
    )
    async def get_device_list() -> str:
        return await tools.get_device_list(thinq_api=thinq_api)
  • Core handler logic for `get_device_list`. Creates a ClientSession, fetches the device list via `thinq_api.async_get_device_list()`, caches it in `local_device_lists`, and formats a human-readable string with device ID, name, type, and model for each device.
    async def get_device_list(thinq_api: ThinQApi) -> List[str]:
        """
        Get device list
        """
        global local_device_lists
        try:
            thinq_api._session = ClientSession()
            if not local_device_lists:
                devices = await thinq_api.async_get_device_list()
                local_device_lists = devices
            else:
                devices = local_device_lists
            device_info = []
            for device in devices:
                device_info.append(
                    f"Device ID: {device.get('deviceId')}\n"
                    f"Device Name: {device.get('deviceInfo').get('alias')}\n"
                    f"Device Type: {device.get('deviceInfo').get('deviceType')}\n"
                    f"Model Name: {device.get('deviceInfo').get('modelName')}\n"
                )
            header = f"Found {len(devices)} devices:\n\n"
            return header + "\n".join(device_info)
    
        except Exception as e:
            return f"An error occurred while retrieving device list: {str(e)}"
Behavior3/5

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

No annotations exist, so the description carries full burden. It discloses a string return type but lacks details on potential pagination, latency, or other behaviors. For a simple list tool, this is acceptable but not exemplary.

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 short and front-loaded, but includes redundant 'Args: None' given the schema. It is efficient but could be slightly tighter.

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

Completeness4/5

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

Given the tool has no parameters and an output schema exists (though not detailed), the description is sufficiently complete for a simple retrieval tool. However, it could mention that the list includes all connected devices.

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?

No parameters exist (0 params, 100% schema coverage). The description states 'Args: None', which confirms the schema but adds no extra meaning beyond it. Baseline 4 is appropriate.

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 'Retrieves a list of all devices' which specifies the action and resource, and is distinct from sibling tools that deal with controls, status, or posting control commands.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or alternatives are provided, but the purpose is clear enough to infer usage. Sibling names offer implicit differentiation, so the guidance is adequate but minimal.

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/thinq-connect/thinqconnect-mcp'

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