Skip to main content
Glama

Get GitOps status

get_gitops_status
Read-only

The GitOps sync state of a cluster (the twin of ankra cluster gitops status): the connected repository and branch with the credential it authenticates with, sync status and phase, the last synced and pending commits, the last error, and two silent-breakage signals the portal's overview hides - credential_missing (the binding names a credential that no longer exists) and source_mismatch (the last sync resolved a different repository than the one configured). Use this before blaming a stack when a change committed to Git has not reached the cluster. Read-only.

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_gitops_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idNoUUID of the target cluster. Optional when a cluster is selected.
cluster_nameNoExact name of the target cluster. Optional when a cluster is selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only supply readOnlyHint, and the description confirms "Read-only" plus adds real substance: the two silent-breakage signals (credential_missing, source_mismatch) that the portal overview hides, and the fact that credential identity is surfaced. It stops short of covering pagination, permissions, or response shape.

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?

One dense but well-structured sentence front-loads what the tool returns, then a second sentence gives the decision rule. Every clause carries information; nothing is restated from the title or annotations.

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?

With no output schema, the description compensates by enumerating the returned fields and the failure signals an agent should look for. It is nearly complete for this read-only diagnostic, with only minor gaps around target-cluster resolution.

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 100% with only two optional cluster selectors, so the schema already carries the parameter meaning. The description adds nothing about cluster_id versus cluster_name or the fallback to a currently selected cluster; baseline 3 applies.

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?

States a specific resource and scope ("The GitOps sync state of a cluster") and enumerates exactly what is returned: connected repository and branch, credential, sync status and phase, last synced and pending commits, last error. It also names a CLI twin, making it easy to distinguish from siblings like get_gitops_conflict_diff or list_gitops_conflicts.

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?

Gives an explicit trigger: "Use this before blaming a stack when a change committed to Git has not reached the cluster." That is clear situational guidance, but it never names an alternative tool or an exclusion (e.g., when to prefer get_gitops_conflict_diff or list_gitops_conflicts instead).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.