mgi-mind

Official

Overview Schema Source Related Servers Discussions Admin

mind_fact_invalidate

Soft-deletes a fact by ID to supersede a changed single-valued fact. Deprecated in v2.0; use the action-based fact invalidation method instead.

Instructions

DEPRECATED: use mind_fact(action="invalidate"). Removed in v2.0. (Soft-delete a fact by ID (for superseding a changed single-valued fact))

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": {
      "id": "<id>"
    },
    "name": "mind_fact_invalidate"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Fact ID from mind_fact_query

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that this is a 'soft-delete' (vs. hard delete) and its intended semantic purpose (superseding a changed single-valued fact), which adds real context beyond the name. However, it omits permissions, reversibility details, and side-effect scope for the mutation.

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?

Front-loaded and efficient: deprecation and replacement come first, purpose follows. Slightly redundant with the nested parentheses around the purpose clause, but no wasted sentences.

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 deprecated single-param tool with no output schema, the essential information an agent needs — that it is deprecated and what to call instead — is fully present. Only minor behavioral detail (permissions, reversibility) is absent.

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 description coverage is 100% and the sole 'id' parameter is documented in the schema ('Fact ID from mind_fact_query'). The description adds no syntax or format detail beyond that, so the baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb+resource ('Soft-delete a fact by ID') and immediately front-loads a deprecation notice pointing to the replacement sibling 'mind_fact(action="invalidate")'. An agent can distinguish this from mind_fact, mind_fact_add and mind_fact_query without opening any schema.

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?

Explicit routing guidance: it names the exact replacement call and states this tool is 'Removed in v2.0'. The when-not-to-use condition and the concrete alternative are both spelled out, leaving nothing to inference.

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