Skip to main content
Glama
Sign In
Semaphore UI MCP server

Semaphore UI MCP server

by johsem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_latest_terraform_state

Read-onlyIdempotent

Retrieve the current Terraform state for a specified Semaphore UI project inventory to inspect deployed infrastructure and verify configuration alignment.

Instructions

get latest terraform state. Availability depends on Semaphore edition, license, and permissions; some Community routes return 404 or empty lists. GET /project/{project_id}/inventory/{inventory_id}/terraform/states/latest.

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": {
      "project_id": "<project_id>",
      "inventory_id": "<inventory_id>"
    },
    "name": "get_latest_terraform_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
inventory_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds real behavioral value beyond that: availability varies by Semaphore edition, license, and permissions, and Community routes may return 404 or empty lists — a non-obvious failure characteristic an agent should anticipate.

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 sentences, front-loaded with the purpose, followed by the availability caveat. The raw endpoint path is slightly redundant but compact and adds routing context. No wasted prose.

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

Completeness4/5

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

For a simple read tool with no output schema and annotations covering the safety profile, the description supplies the key missing piece (partial-availability / 404 behavior). The remaining gap is parameter meaning, only partially filled by the path template.

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 0%, so the two required params are otherwise undocumented. The endpoint template ('/project/{project_id}/inventory/{inventory_id}/...') implicitly maps each parameter to its resource, partially compensating, but adds no detail on valid values or sourcing of IDs.

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?

The description states a specific verb+resource ('get latest terraform state'), and the word 'latest' distinguishes it from siblings like get_terraform_state and list_terraform_states. It doesn't explicitly name those alternatives, so sibling differentiation is only implicit.

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

Usage Guidelines3/5

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

Usage is only implied: fetch the newest state for a given inventory. There is no explicit when-to-use/when-not guidance and no named alternative for retrieving historical states or listing them. Availability caveats are present but describe failure modes, not tool selection.

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