Pathrule

Pathrule Update Memory

pathrule_update_memory

Destructive

Update a memory's content or title, optionally moving it. Uses optimistic concurrency via expected_version_id. Cloud-only.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	No	Optional replacement memory title.
`content`	Yes	Replacement memory body in clear project-language prose.
`memory_id`	Yes	Memory UUID returned by pathrule_get_context, pathrule_goto, or pathrule_read_memory.
`move_to_path`	No	Optional workspace-relative destination path such as /packages/app. Missing nodes are created when allowed by the backend.
`workspace_id`	Yes	Workspace UUID from pathrule_list_workspaces.
`related_paths`	No	Optional list of workspace-relative paths this memory is also relevant to. null = unchanged. Pass [] to clear all manual links. Max 32 entries.
`allow_duplicate`	No	Set true only when intentionally allowing another memory with the same title.
`expected_version_id`	No	Optional optimistic-concurrency token from the existing record. Pass it when available to avoid overwriting a newer edit.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	true when the call succeeded. false when it did not, in which case `error` carries the reason and the success fields are absent.
`data`	No	Updated memory: id, version_id, and the title it now carries.
`error`	No	Present only when ok is false.
`human_message`	No	One-line summary of the result, safe to relay to the user verbatim.
`related_to_check`	No	Up to 3 items that may need the same change (companions, links, near duplicates), from a cached knowledge map.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026

addedOutput schema / properties / related_to_check

Added value: +{
+  "description": "Up to 3 items that may need the same change (companions, links, near duplicates), from a cached knowledge map.",
+  "items": {},
+  "type": "array"
+}

Changed1 schema field changedSep 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "data": {
+      "description": "Updated memory: id, version_id, and the title it now carries."
+    },
+    "error": {
+      "additionalProperties": true,
+      "description": "Present only when ok is false.",
+      "properties": {
+        "code": {
+          "description": "Stable machine-readable failure code, for example insufficient_scope, workspace_id_required, rate_limited, not_found, or upstream_error. Branch on this, not on message text.",
+          "type": "string"
+        },
+        "detail": {
+          "description": "Optional structured context for the failure, for example { missing_scopes: [...] } on insufficient_scope."
+        },
+        "message": {
+          "description": "Human-readable explanation of the failure.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "human_message": {
+      "description": "One-line summary of the result, safe to relay to the user verbatim.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "true when the call succeeded. false when it did not, in which case `error` carries the reason and the success fields are absent.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

First observedMay 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotency, so the safety profile is covered. The description goes further by disclosing the optimistic-concurrency contract via expected_version_id and the cloud-only deployment constraint, which are not derivable from annotations. It still does not say that content fully replaces the existing body or what permission is required.

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

Conciseness5/5

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

Three short sentences, front-loaded with the core action before the concurrency mechanism and deployment constraint. No filler or redundancy.

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?

An output schema exists so return values need not be explained, and the description covers scope plus the two non-obvious operational traits (concurrency token, cloud-only). It is nearly complete for an 8-parameter mutation tool, lacking only permission/overwrite specifics.

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%, so every one of the 8 parameters is already documented in the schema (including the null-vs-[] semantics for related_paths). The description only re-references expected_version_id at a high level, adding no syntax or format detail beyond the schema, so the baseline 3 applies.

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 and resource ("Update a memory's content or title") and adds the optional move capability, so the agent knows exactly what operation this performs. It does not, however, distinguish itself from close siblings like pathrule_write_memory or the update_rule/update_skill family, so no credit for sibling differentiation.

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?

"Cloud-only" gives one real usage precondition, and "Update a memory's content" implies this is for existing records (unlike pathrule_write_memory), but the alternative is never named and there are no explicit when/when-not statements. Usage is implied rather than stated.

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

All Pathrule tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?