Skip to main content
Glama
Sign In
Semaphore UI MCP server

Semaphore UI MCP server

by johsem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_cluster_status

Read-onlyIdempotent

Retrieves the current Semaphore UI cluster status from the management API so you can verify cluster health and availability.

Instructions

get Cluster Status. GET /cluster.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_cluster_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds nothing beyond the endpoint path: no indication of what the status payload reveals, freshness, or whether it is expensive/slow against a live cluster.

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

Conciseness3/5

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

Two short fragments with no filler, but the second fragment ('GET /cluster') only duplicates implementation detail an agent cannot act on, and the whole is arguably too terse to be an adequate definition rather than efficiently written.

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?

For a zero-param read tool with no output schema and a crowded sibling set of cluster/system/admin info tools, the description should say what the response covers and when it is the right source. Neither is provided, so an agent cannot confidently choose this tool.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies by rule.

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

Purpose2/5

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

"get Cluster Status" essentially restates the tool name, and "GET /cluster" only names the underlying endpoint. It never says what 'status' means (health, workers, version, queue) or how it differs from siblings like get_system_info, get_admin_info, or get_server_options.

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 when-to-use guidance, no exclusions, and no mention of the near-identical informational siblings. An agent has to guess whether this or get_system_info/get_admin_info is the right call for cluster-level diagnostics.

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