Pathrule

Pathrule Write Memory

pathrule_write_memory

Create a new memory at a workspace path. Missing nodes auto-create. Blocks duplicate titles unless allow_duplicate is set. Cloud-only: never writes to the user's local filesystem. For automatic CLAUDE.md/AGENTS.md sync and on-disk hook injection alongside the write, install Pathrule Studio or CLI.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	Short specific title. It is the duplicate key for this node, so make it the thing being remembered, not a category.
`source`	No	Who authored the memory: claude when an agent wrote it, manual when the user dictated it. Defaults to claude.
`content`	Yes	The memory body: the decision, convention, or bug pattern worth remembering, and why it matters.
`node_path`	Yes	Workspace-relative path, e.g. /apps/api.
`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 = no links. Max 32 entries.
`allow_duplicate`	No	Set true only when a second memory with the same title on this node is intentional. Leave unset so near-duplicates are rejected.

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	Created memory: id, title, node_id, node_path, version_id.
`error`	No	Present only when ok is false.
`warnings`	No	Non-fatal notices, for example a near-duplicate title that was allowed through.
`human_message`	No	One-line summary of the result, safe to relay to the user verbatim.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed5 schema fields changedSep 5, 2026

addedInput schema / properties / allow_duplicate / description

Added value: +"Set true only when a second memory with the same title on this node is intentional. Leave unset so near-duplicates are rejected."

addedInput schema / properties / content / description

Added value: +"The memory body: the decision, convention, or bug pattern worth remembering, and why it matters."

addedInput schema / properties / source / description

Added value: +"Who authored the memory: claude when an agent wrote it, manual when the user dictated it. Defaults to claude."

addedInput schema / properties / title / description

Added value: +"Short specific title. It is the duplicate key for this node, so make it the thing being remembered, not a category."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "data": {
+      "description": "Created memory: id, title, node_id, node_path, version_id."
+    },
+    "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"
+    },
+    "warnings": {
+      "description": "Non-fatal notices, for example a near-duplicate title that was allowed through.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

First observedMay 27, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description discloses several important behaviors: missing nodes auto-create, duplicate titles are blocked unless allow_duplicate is set, and the tool is cloud-only and never writes to the user's local filesystem. These are non-obvious operational details an agent needs to predict the tool's side effects correctly.

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?

The description is compact and front-loaded: the main action comes first, followed by behavioral rules and a critical cloud-only constraint. The final sentence about Pathrule Studio/CLI is relevant context for users expecting local sync, and it doesn't bloat the description. Every sentence earns its place.

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?

Given the rich input schema (100% parameter coverage), existing output schema, and annotations, the description is complete enough for correct invocation. It adds the missing behavioral context—auto-creation, duplicate blocking, cloud-only execution—that an agent couldn't infer from the structured fields alone. No critical call-time decision is left undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all seven parameters well. The description adds value beyond the schema by explaining that missing nodes auto-create (relevant to node_path) and that duplicate titles are blocked unless allow_duplicate is set (reinforcing title's duplicate-key semantics). It doesn't need to repeat parameter details already in 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?

The description opens with a specific verb-resource pair, 'Create a new memory at a workspace path,' which clearly distinguishes this from sibling tools like pathrule_read_memory, pathrule_update_memory, pathrule_write_rule, and pathrule_write_skill. It also adds key scoping details (workspace path, new memory, duplicate rejection) that make its role unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for what this tool does and when it applies: creating a new memory at a workspace path, with auto-creating nodes and duplicate blocking. It doesn't explicitly name alternatives like pathrule_update_memory for modifying existing memories, but the 'new memory' phrasing strongly implies the boundary, and the cloud-only caveat gives a concrete environmental constraint.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation4/5

Tools are grouped by resource (memory/rule/skill/workspace/snapshot/refresh) and mostly have distinct output shapes, so agents can usually pick the right one. A few retrieval tools (get_context, get_node, get_tree, goto) overlap in purpose, but their descriptions clarify resolution mode vs full tree vs context bundle.

Naming Consistency3/5

All tools share the pathrule_ prefix and mostly follow verb_noun, but the verbs are inconsistent: create_workspace vs write_memory, get_node vs read_memory, delete_skill vs remove_pattern, plus verb-only exceptions like goto, setup, and ping. The pattern is readable but not uniform.

Tool Count2/5

32 tools is above the 25-tool threshold and feels heavy for a single server, even with a broad domain. Several context-retrieval tools and read/list variants could potentially be consolidated, though each tool does have a specific purpose.

Completeness4/5

Core CRUD is covered for memories, rules, and skills, along with workspaces, snapshots, refresh tasks, and pattern import/removal. Minor gaps include no standalone list_rules/list_skills and no snapshot update/delete, but agents can work around these via get_context, goto, and get_tree.

Resources

Need Help?