Skip to main content
Glama
cobanov

teslamate-mcp

get_battery_health_summary

Retrieve battery health status and statistics for Tesla vehicles from TeslaMate data, enabling monitoring of battery condition and performance metrics.

Instructions

Get the battery health summary for each car. Provides current battery health status and statistics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:22-28 (handler)
    Factory that creates the handler function for the tool, which executes the associated SQL query ('battery_health_summary.sql') synchronously using the database manager.
    def create_tool_handler(sql_file: str):
        """Factory function to create tool handlers"""
    
        def handler() -> List[Dict[str, Any]]:
            return db_manager.execute_query_sync(sql_file)
    
        return handler
  • main.py:31-39 (registration)
    Dynamically creates and registers the tool handler for 'get_battery_health_summary' (and others) with the FastMCP server.
    # Register all tools from definitions
    for tool_def in TOOL_DEFINITIONS:
        tool_func = create_tool_handler(tool_def.sql_file)
        tool_func.__doc__ = tool_def.description
        tool_func.__name__ = tool_def.name
    
        # Register the tool with the MCP server
        mcp.tool()(tool_func)
  • src/tools.py:37-41 (registration)
    ToolDefinition that registers 'get_battery_health_summary' with its description and SQL file path.
    ToolDefinition(
        name="get_battery_health_summary",
        description="Get the battery health summary for each car. Provides current battery health status and statistics.",
        sql_file="battery_health_summary.sql",
    ),
  • Handler function for predefined tools in the remote HTTP server, which loads the ToolDefinition and executes the SQL query asynchronously.
    async def execute_predefined_tool(tool_name: str) -> List[Dict[str, Any]]:
        """Execute a predefined tool by name"""
        if not app_context:
            raise RuntimeError("Application context not initialized")
    
        tool = get_tool_by_name(tool_name)
        return await app_context.db_manager.execute_query_async(
            tool.sql_file, app_context.db_pool
        )
  • Defines the input schema (empty object, no parameters) and registers the tool in the list_tools() for the remote server.
    for tool_def in TOOL_DEFINITIONS:
        tools.append(
            types.Tool(
                name=tool_def.name,
                description=tool_def.description,
                inputSchema={"type": "object", "properties": {}},
            )
        )
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 mentions the tool 'provides current battery health status and statistics' which suggests a read-only operation, but doesn't specify format, scope (all cars vs filtered), response structure, or any limitations. For a tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 perfectly concise with two sentences that each add value. The first sentence states the core purpose, the second adds important detail about what's provided. No wasted words, no redundancy, and front-loaded with the main action.

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 the tool has 0 parameters, 100% schema coverage, and an output schema exists, the description is reasonably complete for its purpose. However, with no annotations and multiple sibling tools in the same domain, it should ideally provide more context about when this summary tool is appropriate versus other battery-related tools. The existence of an output schema means the description doesn't need to explain return values.

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 parameter situation. The description appropriately doesn't discuss parameters since none exist. Baseline for 0 parameters with full schema coverage is 4, as the description correctly avoids redundant parameter information.

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 action ('Get') and resource ('battery health summary for each car'), specifying it provides status and statistics. It distinguishes from siblings like 'get_battery_degradation_over_time' by focusing on current status rather than historical trends. However, it doesn't explicitly differentiate from all battery-related tools like 'get_daily_battery_usage_patterns'.

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. With multiple battery-related siblings (get_battery_degradation_over_time, get_daily_battery_usage_patterns), there's no indication of when this summary tool is preferred over more specific battery tools. No prerequisites or exclusions are mentioned.

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/cobanov/teslamate-mcp'

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