Mirsad

remember_fact

Stores a fact about a subject and predicate, closes the prior value instead of deleting it, and flags a conflict for user resolution when another agent overwrites it.

Instructions

Store a fact about a subject. If another value is currently recorded for the same subject+predicate, the old one is closed (not deleted) and, when a different agent overwrites it, a conflict is opened for the user. Always pass your own assistant name as agent.

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": {
      "subject": "<subject>",
      "predicate": "<predicate>",
      "value": "<value>",
      "agent": "<agent>"
    },
    "name": "remember_fact"
  }
}

Input Schema

Name	Required	Description	Default
`agent`	Yes
`value`	Yes
`subject`	Yes
`predicate`	Yes
`source_ref`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

A3.6/5.0

Behavior4/5

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

No annotations are present, so the description carries the full burden and does substantial work: it discloses supersede semantics (old value is closed, not deleted) and the cross-agent conflict-opening behavior shown to the user. It omits idempotency, permissions, and what the call returns, which keeps it from a 5.

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?

Three tight sentences, front-loaded with what is stored followed by the side effects, then the mandatory `agent` instruction. No filler, though the semicolon-heavy second sentence is slightly dense.

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?

For a write tool with no annotations and no output schema, the overwrite/conflict behavior is the key thing to disclose and it is covered. Gaps remain around the return shape (whether a conflict or fact id comes back), conflict visibility timing, and the `source_ref` parameter.

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 coverage is 0%, so the description must compensate. It correctly explains the composite subject+predicate semantics and gives explicit guidance for `agent` (pass your own assistant name), but leaves `source_ref` and the meaning of `value` undocumented.

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?

States a specific verb and resource ("Store a fact about a subject") and adds scope via the subject+predicate key. It does not name or differentiate itself from siblings like current_fact or record_decision, so an agent must infer the boundary.

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 subject+predicate framing implies when this tool applies, and the overwrite note hints at the difference from a read like current_fact, but there is no explicit when-to-use/when-not-to-use and no named alternative such as record_decision or record_outcome.

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

Deploy Server