Skip to main content
Glama
server-noonien

server-noonien

Official

Resolve Conflict

resolve_conflict
Destructive

Settle a conflicting observation or relation by keeping or dropping it with a newer stamp, so every node adopts the decision as changes propagate.

Instructions

Settle an element that more than one machine has written: keep it or drop it with a stamp newer than anything in the log, so the decision wins on every node as the change propagates. Use it after read_conflicts named the element and you have decided how it should stand — re-creating it with the existing tools is not enough, because a write that already exists is skipped, and deleting what is already tombstoned changes nothing. An element that already stands as you ask is left untouched and reported as unchanged, because every write is durable history. An observation needs the entity to exist, and a relation both of its endpoints, exactly as when they were created.

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": {
      "elements": "<elements>"
    },
    "name": "resolve_conflict"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementsYesOne entry per element: an observation or a relation, and whether it stands

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A4/5.0
Behavior1/5

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

The description adds substantial behavior beyond annotations: conflict stamps, propagation, durable history, no-op handling, and existence prerequisites. However, it says an element already in the requested state is left untouched and reported as unchanged, which describes idempotent behavior, while the annotations declare idempotentHint=false. That direct conflict requires a score of 1 under the annotation-contradiction rule.

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?

The definition is front-loaded with purpose and each sentence carries useful information about alternatives, no-op behavior, or prerequisites. It is somewhat dense and long-sentenced, but there is little outright waste.

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 annotations and an output schema present, the description does not need to explain return values, and it covers the key conflict semantics, usage trigger, no-op behavior, and prerequisites. Nothing essential for calling the tool correctly is omitted.

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?

Schema description coverage is 100%, so the schema already documents keep and the observation/relation fields. The description adds useful semantics beyond the schema: an observation requires its entity to exist, a relation requires both endpoints, and keep maps to making the element stand or go.

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?

The description uses a specific verb and resource: settle an element written by multiple machines, keeping or dropping it. It also distinguishes the operation from sibling write paths by explaining that re-creating or deleting will not resolve the conflict.

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?

It gives an explicit trigger: use after read_conflicts has named the element and the desired state has been decided. It also identifies inadequate alternatives, stating that re-creating is not enough and deleting an already-tombstoned element changes nothing.

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