Skip to main content
Glama
linkcd
by linkcd

get_price_and_home_info

Retrieve current and forecasted electricity prices with breakdowns, price levels, and home information including address and timezone from your Tibber energy account.

Instructions

Get the infomation of: 1. current price, with price break down, price level, and currency 2. hourly price and price level of today 3. hourly price and price level of tomorrow 4. home address info, timezone etc the currency is applying to all prices

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.py:21-47 (handler)
    The main handler function that implements the 'get_price_and_home_info' tool logic. It connects to the Tibber API, fetches home and price information, and returns it as a string.
    async def get_price_and_home_info() -> str:
        """Get the infomation of:
            1. current price, with price break down, price level, and currency
            2. hourly price and price level of today
            3. hourly price and price level of tomorrow
            4. home address info, timezone etc
        the currency is applying to all prices
        """
        try:
            tibber_connection = tibber.Tibber(tibber_api_token, user_agent="tibber-mcp")
            await tibber_connection.update_info()
            
            homes = tibber_connection.get_homes()
            if not homes:
                logger.error("No homes found for this Tibber account")
                return "No homes found"
            
            home = homes[0]
            await home.update_info_and_price_info() #using predefined query UPDATE_INFO_PRICE for getting most of info such as current price, today and tomorrow price, home info and subscription etc
            result = home.info 
    
            await tibber_connection.close_connection()
            return str(result)
        
        except Exception as e:
            logger.error(f"Error retrieving price info: {e}")
            return f"Error: {str(e)}"
  • server.py:20-20 (registration)
    The @mcp.tool() decorator registers the get_price_and_home_info function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It describes what data is returned but doesn't mention whether this is a read-only operation, potential rate limits, authentication needs, or error conditions. It lacks critical behavioral context for an agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured as a bulleted list which helps organization, but contains minor spelling errors ('infomation') and could be more front-loaded. The information is reasonably concise but not optimally polished.

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?

For a tool with no parameters and no output schema, the description adequately explains what data is returned (price breakdowns, home info). However, without annotations or output schema, it should ideally provide more behavioral context about the operation's characteristics and return format.

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 tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the empty parameter set. The description appropriately doesn't discuss parameters, maintaining focus on what the tool returns rather than what it accepts.

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 retrieves price information (current, hourly today/tomorrow) and home address/timezone data. It specifies the verb 'Get' and resources (price data, home info), though it doesn't explicitly differentiate from the sibling tool 'get_consumption_data'.

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 is provided on when to use this tool versus the sibling 'get_consumption_data'. The description lists what data is retrieved but doesn't specify use cases, prerequisites, or alternatives.

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/linkcd/tibber-mcp'

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