Skip to main content
Glama
madorn
by madorn

get_bridge_info

Retrieve Bond Bridge device information including version, uptime, and configuration details for smart home device management.

Instructions

Get Bond Bridge information and status.

Returns: Bridge information including version, uptime, and configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler for 'get_bridge_info', decorated with @mcp.tool(). It fetches bridge information from the Bond client and augments it with server configuration details.
    @mcp.tool()
    async def get_bridge_info() -> Dict[str, Any]:
        """Get Bond Bridge information and status.
        
        Returns:
            Bridge information including version, uptime, and configuration.
        """
        try:
            async with await get_bond_client() as client:
                bridge_info = await client.get_bridge_info()
                return {
                    "bridge": bridge_info,
                    "server_config": {
                        "host": config.bond_host,
                        "timeout": config.timeout,
                        "max_retries": config.max_retries
                    }
                }
        except BondAPIError as e:
            return {"error": f"Failed to get bridge info: {str(e)}"}
        except Exception as e:
            logger.error(f"Unexpected error getting bridge info: {e}")
            return {"error": f"Unexpected error: {str(e)}"}
  • The BondClient class method that executes the HTTP GET request to the Bond Bridge root endpoint to retrieve bridge information.
    async def get_bridge_info(self) -> Dict[str, Any]:
        """Get Bond Bridge information."""
        return await self._request("GET", "")
  • Pydantic model defining the structure of Bond Bridge information, matching the fields returned by the Bond API.
    class BridgeInfo(BaseModel):
        """Bond Bridge information model."""
        name: str
        location: Optional[str] = None
        bluelight: Optional[bool] = None
        mac: Optional[str] = None
        fw_ver: Optional[str] = None
        hw_ver: Optional[str] = None
        uptime_s: Optional[int] = None
        api: Optional[str] = None
        target: Optional[str] = None
Behavior3/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. It states the tool 'Get Bond Bridge information and status' and mentions return values, implying a read-only operation, but doesn't disclose behavioral traits like authentication needs, rate limits, or error handling. The description adds basic context but lacks depth for a tool with no annotation support.

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 front-loaded with the core purpose in the first sentence, followed by a brief note on returns. Both sentences are necessary and add value, with no wasted words. It's appropriately sized for a simple tool with no parameters.

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 complexity (0 parameters, no annotations, but with an output schema), the description is reasonably complete. It states the purpose and hints at return values, though it could benefit from more behavioral context. The output schema reduces the need to explain returns, but the lack of annotations means the description should do more to cover operational aspects.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. It mentions return values, but since an output schema exists, this isn't required. The baseline for 0 parameters is 4, as the description doesn't need to compensate for any gaps.

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: 'Get Bond Bridge information and status.' It specifies the verb ('Get') and resource ('Bond Bridge information and status'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_device_info' or 'get_device_state', which might also retrieve information about devices.

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 sibling tools like 'get_device_info' or 'get_device_state', nor does it specify any context or prerequisites for usage. This leaves the agent without clear direction on tool selection.

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