Skip to main content
Glama

generate_vhal_pr_message

Generate a structured pull request message for implementing a VHAL property, covering property details, implementation changes, testing, and review checklist.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
areasNo
groupYes
unitsNo
accessYes
max_valueNo
min_valueNo
change_modeYes
descriptionYes
enum_valuesNo
jira_ticketNo
property_idYes
dependenciesNo
property_nameYes
property_typeYes
sample_rate_hzNo
breaking_changeNo
reviewer_suggestionsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are present, so description must carry the burden. It discloses output format ('structured, professional PR description'), includes itemized content, and notes the result is 'ready to copy-paste'. It does not describe side effects or limitations, but for a text generation tool this is acceptable.

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?

Description is appropriately sized for 17 parameters, with a clear first sentence and structured Arg/Returns sections. Each line adds value; no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Combined with schema and output schema context, the description provides sufficient information for correct invocation. It covers purpose, all parameters, and return value. No obvious gaps.

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?

Schema description coverage is 0%, but description provides an Args section with each parameter, including type examples, optionality, and context. This fully compensates for the schema's lack of descriptions and adds meaning.

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?

Description uses specific verb 'Generate' and identifies resource 'pull request message for VHAL property implementation'. Clearly distinguishes from sibling tools that focus on code generation, validation, or analysis.

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?

Description implies tool is used when a copy-paste-ready PR message is needed for VHAL property implementation. It does not explicitly discuss alternative tools or exclusions, but the context is clear enough for 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/feevlic/vhal-mcp-server'

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