Skip to main content
Glama
madorn
by madorn

get_device_info

Retrieve detailed capabilities and properties for a specific Bond Bridge smart home device to enable AI-assisted control and management.

Instructions

Get detailed information about a specific device.

Args: device_id: The Bond device identifier

Returns: Detailed device information including capabilities and properties.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler decorated with @mcp.tool(). It creates a BondClient, calls get_device_info on it, and returns the device information or error.
    @mcp.tool()
    async def get_device_info(device_id: str) -> Dict[str, Any]:
        """Get detailed information about a specific device.
        
        Args:
            device_id: The Bond device identifier
            
        Returns:
            Detailed device information including capabilities and properties.
        """
        try:
            async with await get_bond_client() as client:
                device_info = await client.get_device_info(device_id)
                return {
                    "device_id": device_id,
                    "info": device_info
                }
        except BondAPIError as e:
            return {"error": f"Failed to get device info: {str(e)}"}
        except Exception as e:
            logger.error(f"Unexpected error getting device info: {e}")
            return {"error": f"Unexpected error: {str(e)}"}
  • BondClient helper method that sends a GET request to the Bond Bridge API endpoint /v2/devices/{device_id} to fetch the device information.
    async def get_device_info(self, device_id: str) -> Dict[str, Any]:
        """Get detailed information about a specific device.
        
        Args:
            device_id: Device identifier
            
        Returns:
            Device information
        """
        return await self._request("GET", f"devices/{device_id}")
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. It states the tool retrieves 'detailed information' but doesn't specify whether this is a read-only operation (implied by 'Get'), what permissions are required, if there are rate limits, or the response format beyond 'including capabilities and properties'. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

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 sized and front-loaded, with the core purpose in the first sentence and additional details in a structured 'Args' and 'Returns' section. Every sentence adds value, but the 'Returns' section is somewhat redundant given the presence of an output schema, slightly reducing efficiency.

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's low complexity (1 parameter, no nested objects) and the presence of an output schema (which handles return values), the description is mostly complete. It covers the purpose and parameter semantics adequately. However, it lacks usage guidelines and behavioral details, which are minor gaps in this context.

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 beyond the input schema. The schema has 0% description coverage and only defines 'device_id' as a string, but the description specifies it as 'The Bond device identifier', clarifying its purpose and format. With 1 parameter and low schema coverage, this compensation is effective, though it could be more detailed (e.g., example format).

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 ('Get') and resource ('detailed information about a specific device'), distinguishing it from siblings like 'list_devices' (which likely lists multiple devices) and 'get_device_state' (which might focus on state rather than comprehensive information). However, it doesn't explicitly differentiate from 'get_bridge_info', which could be a similar info-retrieval tool for a different resource.

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 a device_id from 'list_devices'), exclusions (e.g., not for bridges), or comparisons with siblings like 'get_device_state' (which might be for real-time state vs. static properties). The context is implied but not explicit.

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/madorn/bond-mcp-server'

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