Skip to main content
Glama
cortex-local-memory

cortex-local-memory

cortex_memory_delete_batch

Delete multiple memory entries from the cortex knowledge base by their IDs to remove obsolete or unwanted notes in one batch.

Instructions

Delete multiple memory entries from the cortex knowledge base by their IDs

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": {
      "ids": "<ids>"
    },
    "name": "cortex_memory_delete_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesList of memory IDs to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing beyond the bare action. For a destructive bulk mutation it says nothing about irreversibility, whether deletion is atomic or partial on failure, what happens to nonexistent IDs, permission requirements, or whether any confirmation is expected.

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?

One front-loaded sentence with the action first and the scope qualifier second; there is no filler or redundancy. It is appropriately sized, though that brevity is partly the source of the disclosure gaps noted above.

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

Completeness2/5

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

With no annotations, no output schema, and a destructive bulk operation, the description should cover outcome behavior (partial success, missing IDs, irreversibility) and it does not. The parameter side is complete thanks to the schema, but the mutation-risk side is materially under-described for a tool that deletes data in volume.

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 a single required parameter with 100% schema description coverage ("List of memory IDs to delete"), so the schema already does the explanatory work. The description's "by their IDs" restates rather than extends that, adding no format, cardinality, or validation detail beyond the schema.

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?

The description names a specific verb ("Delete"), a specific resource ("memory entries in the cortex knowledge base"), and a scope qualifier ("multiple ... by their IDs") that implicitly separates it from a single-entry delete sibling. It stops short of naming that sibling, so an agent must infer the batch-vs-single distinction from the word "multiple" alone.

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 phrase "multiple ... entries" implies this tool is for bulk removal rather than one-off deletion, which is the only routing signal present. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. the single-entry delete tool), and no guidance on batch size limits or preconditions.

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