Skip to main content
Glama

generate_vhal_implementation_code

Generate VHAL property implementation code for AAOS with all required files, configs, tests, and docs. Just specify property parameters to produce complete implementation.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
areasNo
groupYes
unitsNo
accessYes
max_valueNo
min_valueNo
change_modeYes
descriptionYes
enum_valuesNo
property_idYes
dependenciesNo
property_typeYes
sample_rate_hzNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries the transparency burden. It explains what is produced (files, configurations, tests, documentation) and that the return includes a summary and guide. However, it does not disclose potential side effects, prerequisites (e.g., AAOS source tree access), or whether files are written versus returned as text.

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 long but well-structured with clear Args and Returns sections. It front-loads the core purpose and each parameter gets exactly one line. No redundant sentences; every detail earns its place given the tool's complexity.

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?

For a 14-parameter generator with an output schema, the description covers all inputs and states the return value. It misses minor constraints like validation rules or interactions between parameters, but the output schema and the detailed arg list provide sufficient context for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description lists every parameter with a short explanation and concrete examples (e.g., `HVAC_STEERING_WHEEL_HEAT`, `0x15400A03`). This fully compensates for the sparse schema which has no property descriptions. It adds clarity on formats, defaults, and relationships (e.g., enum_values for INT32 properties).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Generate complete VHAL property implementation code for Android Automotive OS (AAOS).' It clearly distinguishes this from sibling tools like analyze, validate, or summarize by focusing on generation. The scope ('from scratch') further defines its role.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states the tool is used when a new VHAL property must be implemented from scratch, which is clear context. It does not explicitly exclude alternatives or name them, but the purpose and inputs make the intended usage obvious given the sibling list.

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

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