Skip to main content
Glama

Set the preferred Assist pipeline

voice_set_preferred_pipeline
Idempotent

Sets the default Assist pipeline used when no pipeline is specified, so voice commands route through the chosen pipeline.

Instructions

Set the default Assist pipeline, used when no pipeline is specified.

Calls WS assist_pipeline/pipeline/set_preferred.

Use when: changing which pipeline Assist uses by default. Not for: reading the current preference — use voice_list_pipelines, whose response includes preferred_pipeline. Returns: {"preferred_pipeline": pipeline_id} (Home Assistant itself answers with no payload).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pipeline_id": "<pipeline_id>"
    },
    "name": "voice_set_preferred_pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
pipeline_idYesID of the pipeline to make preferred, from `voice_list_pipelines`.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.25.1
    • addedInput schema / properties / pipeline_id / description
      Added value: +"ID of the pipeline to make preferred, from `voice_list_pipelines`."
  2. Addedv0.4.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), but the description adds the underlying WebSocket command `assist_pipeline/pipeline/set_preferred` and notes that Home Assistant returns no payload, so the tool synthesizes the result. That is real behavioral context beyond the structured fields, though error/failure modes and permission requirements go unmentioned.

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

Conciseness4/5

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

The definition is short, label-structured (Use when / Not for / Returns), and front-loads the actual behavior. There is mild redundancy between the opening sentence and the "Use when" line, both of which restate "default pipeline," which keeps it just short of perfect.

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?

For a one-parameter idempotent mutation with full schema coverage and annotations, nothing an agent needs is missing: purpose, scope, alternative, and the WS call are all stated. The Returns line duplicates an existing output schema, but it is harmless surplus rather than a gap.

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

Parameters3/5

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

Schema description coverage is 100% for the single `pipeline_id` parameter, and the schema itself already says it comes from `voice_list_pipelines`. The description reinforces that provenance indirectly but adds no format, validation, or edge-case meaning beyond the schema, so the baseline of 3 applies.

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+resource ("Set the default Assist pipeline") and immediately scopes it ("used when no pipeline is specified"). It also explicitly separates itself from the read path, naming `voice_list_pipelines` as the tool that shows the current preference, so the agent can distinguish it from sibling tools without inspecting schemas.

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

Usage Guidelines5/5

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

It provides an explicit "Use when" clause and a "Not for" exclusion that names the correct alternative and even points at the field (`preferred_pipeline`) that answers the excluded case. This is the full when/when-not/alternative triad with no inference required.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools