Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PYTHONPATHNoPython path for the vHAL MCP server module

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
summarize_vhalC

Summarize vHAL implementation based on a question.

Args:
    question: Question about vHAL implementation

Returns:
    Summary of relevant vHAL information from Android documentation
lookup_android_source_codeA

Lookup Android source code for a given keyword.

Args:
    keyword: Search term (e.g., "SEAT", "HVAC", "vehicle properties")
    category: Category to focus search on (default: "vhal")

Returns:
    Detailed information about the source code location and content
discover_related_propertiesA

Discover related properties, dependencies, and implementation order for vHAL properties.

Args:
    property_or_category: Property name (e.g., "SEAT_MEMORY_SELECT") or category (e.g., "SEAT_MEMORY", "HVAC_BASIC")

Returns:
    Comprehensive analysis of related properties, dependencies, and suggested implementation order
generate_vhal_implementation_codeA

Generate complete VHAL property implementation code for Android Automotive OS (AAOS).

This tool generates all necessary files, configurations, tests, and documentation
needed to implement a new VHAL property from scratch.

Args:
    name: Property name (e.g., "HVAC_STEERING_WHEEL_HEAT")
    property_id: Unique property ID (hex format, e.g., "0x15400A03")
    property_type: Data type (BOOLEAN, INT32, INT64, FLOAT, STRING, BYTES, *_VEC, MIXED)
    group: Property group (HVAC, SEAT, LIGHTS, POWER, CLIMATE, etc.)
    access: Access mode (READ, WRITE, READ_WRITE)
    change_mode: Change mode (STATIC, ON_CHANGE, CONTINUOUS)
    description: Property description for documentation
    units: Optional units (e.g., "celsius", "rpm")
    min_value: Optional minimum value for numeric types
    max_value: Optional maximum value for numeric types
    areas: Optional list of vehicle areas/zones
    enum_values: Optional dict of enum names and values for INT32 enum properties
    dependencies: Optional list of dependent property names
    sample_rate_hz: Optional sample rate for continuous properties

Returns:
    Complete implementation including all generated files, summary, and implementation guide
generate_vhal_pr_messageA

Generate a comprehensive pull request message for VHAL property implementation.

This tool creates a structured, professional PR description that includes all necessary
details about the VHAL property, implementation changes, testing requirements, and
review checklist.

Args:
    property_name: Property name (e.g., "HVAC_STEERING_WHEEL_HEAT")
    property_id: Unique property ID (hex format, e.g., "0x15400A03")
    property_type: Data type (BOOLEAN, INT32, INT64, FLOAT, STRING, BYTES, *_VEC, MIXED)
    group: Property group (HVAC, SEAT, LIGHTS, POWER, CLIMATE, etc.)
    access: Access mode (READ, WRITE, READ_WRITE)
    change_mode: Change mode (STATIC, ON_CHANGE, CONTINUOUS)
    description: Property description for documentation
    units: Optional units (e.g., "celsius", "rpm")
    min_value: Optional minimum value for numeric types
    max_value: Optional maximum value for numeric types
    areas: Optional list of vehicle areas/zones
    enum_values: Optional dict of enum names and values for INT32 enum properties
    dependencies: Optional list of dependent property names
    sample_rate_hz: Optional sample rate for continuous properties
    breaking_change: Whether this introduces breaking changes (default: False)
    jira_ticket: Optional JIRA ticket reference
    reviewer_suggestions: Optional list of specific review points

Returns:
    Complete pull request message ready to copy-paste into GitHub/GitLab
validate_vhal_sources_and_enhance_summaryA

Enhanced vHAL summary with source validation and transparency.

This tool provides an enhanced version of vHAL summaries that includes:
- Source URL validation to ensure information comes from accessible sources
- Confidence scoring based on source accessibility
- Clear citations showing which sources contributed to each piece of information
- Alternative source suggestions for failed URLs
- Transparency about cached vs. live data

Args:
    question: Question about vHAL implementation
    include_source_validation: Whether to validate URLs are accessible (default: True)
    max_sources_to_check: Maximum number of sources to validate (default: 10)
    
Returns:
    Enhanced summary with source citations, validation status, and confidence metrics
analyze_vhal_implementationA

Analyze Android source code to show how a vHAL property is implemented, including actual source code, file locations, and usage examples.

Args:
    property_name: The vHAL property name to analyze (e.g., "HVAC_STEERING_WHEEL_HEAT", "SEAT_MEMORY_SELECT")
    android_version: Optional Android version to analyze (e.g., "android13", "android14", "android15", "android16")
                    If not specified, uses Android 15 as default. Supported versions:
                    - android13: Android 13 (first vHAL introduction)
                    - android14: Android 14 (major vHAL changes)
                    - android15: Android 15 (current stable, default)
                    - android16: Android 16 (latest)

Returns:
    Comprehensive analysis of the property implementation including source code, dependencies, and usage examples
validate_vhal_property_requestA

Validate vHAL property request and recommend using existing Android property or creating VENDOR_ property.

This tool follows Android best practices: check if a property already exists in the latest Android release
(currently Android 16) and either recommend using the existing property or generate a new VENDOR_ property
with proper naming convention.

Args:
    property_name: Requested property name (e.g., "SEAT_MASSAGE_INTENSITY")
    property_description: Description of what the property does
    property_type: Data type (BOOLEAN, INT32, INT64, FLOAT, STRING, BYTES, *_VEC, MIXED) - default: INT32
    group: Property group (HVAC, SEAT, LIGHTS, POWER, VENDOR, etc.) - default: VENDOR
    access: Access mode (READ, WRITE, READ_WRITE) - default: READ_WRITE
    change_mode: Change mode (STATIC, ON_CHANGE, CONTINUOUS) - default: ON_CHANGE
    units: Optional units (e.g., "celsius", "rpm")
    min_value: Optional minimum value for numeric types
    max_value: Optional maximum value for numeric types
    areas: Optional list of vehicle areas/zones
    enum_values: Optional dict of enum names and values for INT32 enum properties
    dependencies: Optional list of dependent property names
    sample_rate_hz: Optional sample rate for continuous properties
    android_version: Android version to check against (default: android16)

Returns:
    Comprehensive validation result with recommendations and implementation guidance

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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/feevlic/vhal-mcp-server'

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