OpenAkashic

Resolve OpenAkashic Conflict

resolve_conflict

Resolve a conflict on a note and propagate the claim trust state.

Recommended verdicts:
- keep: reviewed and retained
- supersede: this claim should remain searchable but demoted
- merge: this claim has been folded into another container

Legacy verdicts `clear` and `pending_review` are still accepted.
Only the note owner or admin token may call this.

Input Schema

TableJSON Schema

Name	Required	Description
`path`	Yes	Note path whose conflict_status to resolve
`comment`	No	Reason for overriding the conflict verdict
`verdict`	Yes	Conflict verdict: keep\|supersede\|merge (legacy: clear\|pending_review)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses that the operation propagates claim trust state, accepts legacy verdicts, and requires owner/admin token. However, it does not specify reversibility, potential side effects on other notes, or what happens to the previous conflict status.

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?

The description is compact, uses bullet points for verdicts, and includes only essential information about legacy support and authorization.

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 an output schema present and a clear description covering auth, verdict meanings, and legacy support, the tool is adequately specified. It does not explicitly state prerequisites (e.g., note must be in conflict state), but this is implied by the tool's purpose.

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 schema covers all params, and the description adds meaning to the 'verdict' param by explaining keep, supersede, merge. This goes beyond the schema's simple list of options. The other params are self-explanatory.

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 'resolve' and identifies the resource 'conflict on a note' with the effect 'propagate the claim trust state'. It clearly distinguishes from sibling tools like dispute_note and confirm_note by focusing on conflict resolution.

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

Usage Guidelines3/5

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

It provides context for when to use (when resolving a conflict) but does not explicitly name alternatives or state when not to use. The mention of owner/admin token is a precondition rather than usage guidance. Recommended verdicts help choose the appropriate call, but there is no explicit comparison to sibling tools.

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

All OpenAkashic tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.