Skip to main content
Glama
Sign In
Homelab MCP Server

Homelab MCP Server

by washyu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

refresh_terraform_service

Idempotent

Refresh Terraform state for a service by hostname to detect configuration drift and align infrastructure with declared configurations.

Instructions

Refresh Terraform state and detect configuration drift

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": {
      "service_name": "<service_name>",
      "hostname": "<hostname>"
    },
    "name": "refresh_terraform_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostnameYesHostname or IP address of the device
passwordNoSSH password (not needed for mcp_admin after setup)
usernameNoSSH username (use 'mcp_admin' for passwordless access after setup)mcp_admin
service_nameYesName of the service to refresh

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.0
    • removedInput schema / properties / port
      Removed value: -{
-  "default": 22,
-  "description": "SSH port (default: 22)",
-  "type": "integer"
-}
  2. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already indicate idempotentHint=true and readOnlyHint=false. The description adds context about drift detection but doesn't disclose details like whether state is overwritten, if it affects running services, or what happens on drift found. Adequate with annotations.

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?

Single sentence, no fluff. Front-loaded with the action. Every word earns its place.

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

Completeness2/5

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

Despite moderate complexity (4 params, no output schema), the description lacks behavioral details, preconditions, error handling, or what happens after refresh. Insufficient for an agent to fully understand tool consequences.

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 documentation covers all parameters at 100%. The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 clearly uses specific verb 'refresh' and resource 'Terraform state', and adds 'detect configuration drift' which distinguishes it from siblings like 'plan_terraform_service' or 'destroy_terraform_service'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when to avoid, or how it relates to similar tools like 'plan_terraform_service' or 'scan_infrastructure_drift'.

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