Skip to main content
Glama

List GitOps conflicts

list_gitops_conflicts
Read-only

List the open GitOps merge conflicts on a cluster: resources that changed in both Git and the cluster record since the last sync. Each entry carries the resource key, kind, both change types, and the resolution state (undecided, or a recorded 'git'/'cluster' choice that converges on the next sync). Use this first to see what conflicts exist before inspecting diffs or resolving. 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": "list_gitops_conflicts"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idNoCluster UUID. Optional when the chat is already scoped to a cluster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the closing 'Read-only' is largely redundant. What the description does add is genuinely useful and not in any structured field: the per-entry shape (resource key, kind, both change types, resolution state) and the semantics of the 'git'/'cluster' resolution converging on the next sync. It does not cover pagination or whether resolved conflicts are excluded from future listings.

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?

Three sentences, front-loaded with the definition of a conflict, followed by return contents and then the routing hint. Dense and readable, with only minor waste in the trailing 'Read-only' that the annotations already assert.

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

Completeness5/5

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

There is no output schema, so the description must carry the return shape, which it does by enumerating the fields of each entry and explaining the two resolution states. Combined with the read-only annotation and a single documented parameter, nothing an agent needs in order to call this correctly is missing.

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 coverage is 100% and there is only one optional parameter, so the schema already carries the meaning of cluster_id including the chat-scoping fallback. The description only gestures at cluster scoping implicitly ('on a cluster') without adding anything the schema does not already say. 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 verb and resource ('List the open GitOps merge conflicts on a cluster') and goes further by defining what counts as a conflict: resources changed in both Git and the cluster record since the last sync. This distinguishes it cleanly from get_gitops_conflict_diff (inspect) and resolve_gitops_conflict (act), which share the same domain vocabulary.

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

Usage Guidelines5/5

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

'Use this first to see what conflicts exist before inspecting diffs or resolving' gives explicit ordering relative to the two sibling tools an agent would otherwise confuse it with. The only thing missing is a when-not condition, but for a read-only listing tool that omission is negligible.

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.