Skip to main content
Glama

Get GitOps conflict diff

get_gitops_conflict_diff
Read-only

Show the stored diff sides for one conflicting resource: git_content (desired state in Git), cluster_content (current cluster record), and base_content (the last state both sides agreed on), with secret values redacted. Use this to compare the sides and explain what diverged before recommending a resolution. Read-only.

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": {
      "resource_key": "<resource_key>"
    },
    "name": "get_gitops_conflict_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
cluster_idNoCluster UUID. Optional when the chat is already scoped to a cluster.
resource_keyYesThe conflict's resource key, e.g. stack:platform/addon:nginx.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

The readOnlyHint annotation already declares the safety profile, and the trailing "Read-only" merely restates it. The genuinely additive detail is that secret values are redacted and that base_content is a previously agreed snapshot rather than a live read, but it doesn't say whether the diff is a cached snapshot at conflict-detection time or refreshed on each call.

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?

Two sentences, front-loaded with the resource and the three fields, followed by the intended use. Every clause carries information; no filler or restatement of the name.

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?

With no output schema, the description compensates by naming and defining the three content fields the caller receives, plus the redaction caveat. For a one-required-parameter read tool, that covers what an agent needs to decide to call it and interpret the result.

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%, so both parameters (cluster_id with its optional-when-chat-scoped rule, and resource_key with the stack:platform/addon:nginx format example) are already fully documented. The description's field explanations describe return content rather than parameter meaning, so it adds nothing beyond the schema here.

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 ("Show") and a bounded resource ("the stored diff sides for one conflicting resource"), then enumerates the three returned fields with their meaning. An agent can distinguish it immediately from the listing tool (list_gitops_conflicts) and the mutation tool (resolve_gitops_conflict) in the sibling set.

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?

"Use this to compare the sides and explain what diverged before recommending a resolution" gives a clear situational trigger and positions it upstream of resolution work. It does not explicitly name resolve_gitops_conflict as the follow-up tool or state when not to use it, so it stops short of full alternative routing.

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.