Skip to main content
Glama
Sign In
homebutler

homebutler

by Higangssh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

install_status

Read-only

Check the status of an installed app, as its containers report it. An app homebutler did not install is not known here

Instructions

Check the status of an installed app, as its containers report it. An app homebutler did not install is not known here

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": {
      "app": "<app>"
    },
    "name": "install_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesApp name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that — the status is a container-reported view and unmanaged apps are unknown — but does not say what happens for an unknown app name (error vs. empty) or what status values look like.

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?

Two short sentences, front-loaded with the core purpose. The second sentence is terse to the point of being slightly cryptic ("is not known here"), but nothing is wasted.

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

Completeness3/5

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

A simple read tool with annotations and no output schema, so the bar is low, but the description never characterizes what a "status" result contains (running/stopped/degraded, per-container vs. aggregate) — the one thing an agent needs to interpret the response of a status tool.

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?

Only one parameter, and the schema documents it at 100% coverage ("App name"). The description adds no further meaning such as accepted name formats or whether the app must match an install_list entry, so baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource ("check the status of an installed app") and adds the qualifier that the status comes from containers. It is distinguishable from install_list (enumerate) and docker_inspect (raw container detail), though it never names those siblings explicitly.

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 second sentence gives an explicit when-not condition: apps not installed by homebutler are invisible here, which routes the agent away from this tool for foreign apps. It stops short of naming an alternative tool (e.g. install_list or docker_inspect) for those cases.

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