Skip to main content
Glama

plur_tensions

Idempotent

Manage contradictions between memory engrams. List, scan, confirm, dismiss, or resolve tensions with LLM-powered detection.

Instructions

Tension lifecycle (#181). Default: list persisted tension records (unresolved first). scan:true runs an LLM contradiction scan, persists NEW detections as records, and skips already-recorded pairs. Lifecycle actions: action:"confirm" (real conflict), action:"dismiss" (false positive — pair suppressed from future scans), action:"resolve" + winner: (loser engram retired). Scan requires OPENAI_API_KEY or OPENROUTER_API_KEY env var, or explicit llm_base_url + llm_api_key args.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoTension record id (T-YYYY-MMDD-NNN) for action mode
scanNoRun an active contradiction scan using an LLM judge. New detections are persisted as tension records; recorded pairs (any status) are skipped. Requires OPENAI_API_KEY or OPENROUTER_API_KEY env var, or explicit llm_base_url + llm_api_key args.
scopeNoFilter by scope
actionNoLifecycle action on a persisted tension record (requires id). confirm: mark real. dismiss: false positive, suppress the pair. resolve: pick winner (requires winner), the losing engram is retired.
domainNoFilter by domain prefix
statusNoList-mode status filter. Default: unresolved records (detected + confirmed).
winnerNoEngram id that wins the tension (action:"resolve" only). The other engram is retired.
persistNoPersist scan detections as tension records (default true). Set false for a dry-run scan that also ignores the recorded-pair suppress list.
llm_modelNoModel name for scan mode (default: gpt-4o-mini)
max_pairsNoMaximum candidate pairs to evaluate in scan mode (default: 50)
batch_sizeNoPairs judged per LLM call in scan mode (default: 5). Set to 1 for sequential single-pair judging.
llm_api_keyNoAPI key for the LLM (scan mode)
llm_base_urlNoOpenAI-compatible API base URL for scan mode (e.g. https://api.openai.com/v1)
min_confidenceNoMinimum confidence threshold for scan mode (0–1, default: 0.7)
temporal_discountNoMultiply judge confidence by a days-apart ladder (same day x1.0 ... 15+ days x0.3) in scan mode (#240). Overrides the config default (tensions.temporal_discount, off by default). The judge prompt already carries recorded dates; enable this only when date-aware judging alone leaves too many temporal-evolution false positives.
Behavior4/5

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

Describes side effects: scan persists new detections, actions mutate records (confirm, dismiss, resolve). Also mentions env var requirement and temporal discount. Annotations already note non-readOnly and idempotent; description adds concrete mutation details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single paragraph of ~150 words, front-loads default behavior. Somewhat dense but each sentence adds value. Could benefit from bullet points or clearer mode separation for readability.

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

Completeness3/5

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

Covers lifecycle and scanning details well, but lacks description of return values/format for list, scan, and actions. With no output schema, the description should indicate what the tool returns to be fully useful.

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 coverage is 100%, baseline 3. Description adds value with contextual details (e.g., scan skips recorded pairs, temporal discount ladder). Not all parameters get extra context, but meaningful added explanation beyond schema.

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 clearly states the tool manages tension lifecycle, with specific modes: listing unresolved tensions, scanning for contradictions, and performing lifecycle actions. It distinguishes from siblings like plur_tensions_purge by covering the full lifecycle.

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?

Provides explicit context for when to use each mode (list default, scan with API key, action with id). Implicitly tells when not to use scan without credentials. Could be improved by explicitly stating when to use alternatives, but current guidance is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/plur-ai/plur'

If you have feedback or need assistance with the MCP directory API, please join our Discord server