Skip to main content
Glama

Get HACS repository details

hacs_get_hacs_repository
Read-onlyIdempotent

Fetch details for one HACS or Marketplace repository by ID, including installed and available versions and metadata, to verify it before installing or updating.

Instructions

Get details about a single HACS / Marketplace repository.

Calls marketplace/repository/info on HA 2026.11+ or hacs/repository/info on older HA, passing repo_id as the repository_id field.

Use when: checking one repository's installed/available version or metadata before installing or updating it. Not for: browsing many repositories at once — use hacs_list_hacs_repositories. Returns: HA's raw repository-info dict, or an error dict. Errors: {"error", "code", "backend", "hint"} when repo_id is unknown (repository_not_found) or the command fails; code unknown_command when neither the Marketplace nor HACS is available.

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": {
      "repo_id": "<repo_id>"
    },
    "name": "hacs_get_hacs_repository"
  }
}

Input Schema

NameRequiredDescriptionDefault
repo_idYesRepository id (the `id` field), e.g. from `hacs_list_hacs_repositories`.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.28.1
    • changedInput schema / properties / repo_id / description
      Previous value: -"HACS repository id, e.g. from `hacs_list_hacs_repositories`."New value: +"Repository id (the `id` field), e.g. from `hacs_list_hacs_repositories`."
  2. Changed1 schema field changedv0.25.1
    • addedInput schema / properties / repo_id / description
      Added value: +"HACS repository id, e.g. from `hacs_list_hacs_repositories`."
  3. First observedv0.3.0

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing backend routing (marketplace/repository/info on HA 2026.11+, hacs/repository/info otherwise), the repo_id-to-repository_id field mapping, and concrete error codes (repository_not_found, unknown_command) with the error dict shape. The only minor omission is whether results are cached or how large the metadata payload is.

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?

Front-loaded purpose followed by labeled Use when / Not for / Returns / Errors blocks, which is easy to scan. The Returns line partially duplicates the existing output schema and could be trimmed, but no sentence is filler.

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 read tool with full schema coverage and an output schema, the description covers purpose, alternatives, backend fallback, and error semantics. Nothing an agent needs to invoke or interpret the call is missing.

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?

Schema coverage is 100% and the single parameter is already documented, so the baseline is 3. The description still adds real value by explaining that repo_id is sent as the `repository_id` field on the wire, which the schema does not say.

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?

Names a specific verb and resource ('Get details about a single HACS / Marketplace repository') and immediately scopes it to one repository, which cleanly separates it from the list/install/update siblings. An agent can identify the operation without opening the schema.

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?

Explicit 'Use when' clause (checking installed/available version or metadata before install/update) plus an explicit 'Not for' that routes to the correct sibling, hacs_list_hacs_repositories. Both the positive and negative selection conditions are stated.

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