Skip to main content
Glama

memory_conflicts

Read-only

Lists unresolved contradictions between stored memories detected by similarity analysis, helping you find and review conflicting information.

Instructions

List unresolved memory conflicts (contradictory memories detected by similarity analysis)

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": "memory_conflicts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.7/5.0
Behavior3/5

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

The readOnlyHint=true and destructiveHint=false annotations already establish the safety profile, so the description's main added value is explaining the origin of the data (conflicts surfaced by similarity analysis). It says nothing about result ordering, count limits, or what state an 'unresolved' conflict is in, which leaves meaningful behavioral gaps for a triage-style tool.

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?

A single front-loaded sentence with the verb first and the clarifying definition parenthetically attached. No filler, no redundancy.

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?

For a zero-parameter, read-only listing tool with annotations covering the safety profile, this is nearly complete. The one remaining unknown is the shape of the returned conflict records, which is not covered by an output schema, but that is a minor omission for a tool of this simplicity.

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?

There are zero parameters and 100% schema coverage, so there is nothing for the description to disambiguate. Baseline for a no-parameter tool applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ("List unresolved memory conflicts") and adds a parenthetical defining what a conflict is ("contradictory memories detected by similarity analysis"). It does not differentiate itself from plausible siblings such as memory_resolve or memory_health, so it stops short of a 5.

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?

The purpose implies the usage case — a read-only listing of outstanding conflicts, presumably a precursor to memory_resolve — but the description never states when to call this versus memory_resolve, memory_health, or memory_search, and gives no prerequisites or follow-up guidance. Usage is inferable but not spelled out.

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