Pathrule

Pathrule Remove Pattern

pathrule_remove_pattern

Remove a previously-imported Pathrule pattern bundle in one call — the reverse of pathrule_import_pattern. The pattern definition is the manifest, so this finds and deletes the memories/rules/skills whose titles match the pattern's pieces. Pass the SAME node_path base used at import (omit if the pattern's own paths were used). Pieces not found are reported, not errors (idempotent). Relay the returned human_message.

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	Yes	Pattern slug — the part after 'package:' in ::pathrule:package:<slug>.
`verbose`	No	Set true for per-piece detail. Default false (compact summary).
`node_path`	No	The base path the bundle was imported under. Must match the import to locate the pieces.
`workspace_id`	Yes	Workspace UUID from pathrule_list_workspaces.

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.
`slug`	No	Pattern slug that was removed.
`error`	No	Present only when ok is false.
`removed`	No	The pieces actually deleted, grouped by kind.
`not_found`	No	Pieces the bundle declares that were not present under the given node_path.
`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.

Changed1 schema field changedSep 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "description": "Compact form by default. With verbose=true the full removal record is spread onto the top level instead.",
+  "properties": {
+    "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"
+    },
+    "not_found": {
+      "description": "Pieces the bundle declares that were not present under the given node_path."
+    },
+    "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"
+    },
+    "removed": {
+      "description": "The pieces actually deleted, grouped by kind."
+    },
+    "slug": {
+      "description": "Pattern slug that was removed.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

AddedJun 9, 2026

TDQS

A3.8/5.0

Behavior1/5

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

The annotations declare idempotentHint=false and destructiveHint=false, while the description explicitly says pieces not found are 'not errors (idempotent)' and that the tool 'deletes the memories/rules/skills.' This is a direct contradiction in both idempotency and destructiveness, making the behavioral guidance unreliable.

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 four sentences, front-loaded with the primary purpose, then gives only behaviorally important details: deletion mechanism, node_path guidance, error behavior, and expected output handling. Every sentence earns its place with no filler.

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?

The description covers the operation, the manifest-matching mechanism, node_path behavior, error handling, and instructs relaying the human_message. Combined with 100% schema coverage and an output schema, this is nearly complete, but the contradictions with annotations undercut overall clarity and make it not fully trustworthy.

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 baseline is 3. The description adds meaningful value beyond the schema by instructing the agent to pass the SAME node_path used at import and to omit it if the pattern's own paths were used, which clarifies a subtle condition the schema only hints at.

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 names the specific resource ('previously-imported Pathrule pattern bundle') and action ('Remove'), and explicitly frames it as the reverse of pathrule_import_pattern. This clearly distinguishes it from sibling delete tools by emphasizing bundle-level removal rather than individual memory/rule/skill deletion.

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 provides clear context: use this tool to remove an entire imported pattern bundle in one call, and it explains the node_path requirement and missing-piece behavior. It does not explicitly state 'use pathrule_delete_memory/rule/skill for individual pieces instead,' but the intent is strongly implied by the bundle-level framing.

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?