AiAkiv Memory

hide_memory

Hide a saved event from all recall — search, neighbors, and derived layers.

Use this when the user says a memory was saved by mistake, landed in the
wrong project, or has been superseded. Do not use it to remove data
permanently: this is a reversible hide rather than a delete, and un-hiding is
an operator action, not a tool.

Writes to an existing record. Events belonging to another team are refused.
A memory that an app manages (for example a work published by an app) cannot
be hidden while that work is archived, or while the account's "Write
directly into app memory" permission is off; only a human can turn that on.

Args:
    event_id: The event to hide.

Returns:
    `{event_id, deprecated, hidden, changed}` — or `{error}` when the id is
    empty, not found, belongs to another org, or is app-managed memory
    (`app_managed_read_only`, `app_memory_write_disabled`).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`event_id`	Yes	The event to hide.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 25, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), it discloses that this is a reversible hide, that it writes to an existing record, that cross-team events are refused, and that app-managed memory is blocked unless a human enables the write permission. It also enumerates the error conditions, which is unusually rich behavioral context.

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 with purpose and routing in the first two sentences, and the behavioral caveats follow logically. The structured Args/Returns blocks are somewhat redundant given the schema and existing output schema, but the prose itself is tight.

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

Completeness5/5

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

For a single-parameter mutation tool with annotations and an output schema, the description covers purpose, alternatives, reversibility, auth/permission constraints, and error cases. Nothing an agent needs to invoke it correctly is missing.

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?

There is only one parameter and schema coverage is 100%, so the schema already carries the semantics; the description merely restates 'event_id: The event to hide.' Per the baseline for high schema coverage, a 3 is appropriate, and it adds no format or syntax detail beyond the 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?

States a specific verb (hide) and resource (a saved event/memory) and pins the scope precisely: 'from all recall — search, neighbors, and derived layers.' This clearly distinguishes it from siblings like update_memory, save_memory, and the search/query tools.

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?

Explicitly names when to use it (memory saved by mistake, landed in wrong project, superseded) and when not to (permanent removal), and clarifies that un-hiding is an operator action rather than a sibling tool. Nothing is left to inference.

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

All AiAkiv Memory tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.