Pathrule

Create Pathrule Workspace

pathrule_create_workspace

Create a new Pathrule workspace inside an organization. Cloud-only: writes the workspace row through the user's JWT (RLS enforces organization membership). Does NOT attach the workspace to a local folder, does NOT install any AI client config, and does NOT render CLAUDE.md/AGENTS.md or editor companion files — those steps require Pathrule Studio or CLI. After creation, call pathrule_setup with the returned workspace_id to fetch the bootstrap brief.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Human-readable workspace name (e.g. the project / repo display name).
`git_remote_url`	No	Optional git remote URL (HTTPS or SSH form). Stored for reference and surface matching; never used to access the user's machine.
`organization_id`	Yes	Organization UUID from pathrule_list_organizations.
`active_agent_targets`	No	AI clients this workspace will be used from. Affects Desktop/CLI companion file rendering when those surfaces attach. Defaults to ['claude-code'].

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	The created workspace row.
`error`	No	Present only when ok is false.
`next_step`	No	The call to make next, as { tool, arguments }.
`human_message`	No	One-line summary of the result, safe to relay to the user verbatim.
`local_runtime`	No	Present on tools that carry the local-runtime upgrade reminder.

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,
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "description": "The created workspace row.",
+      "properties": {
+        "active_agent_targets": {
+          "anyOf": [
+            {
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "AI clients this workspace is configured for."
+        },
+        "created_at": {
+          "description": "Creation timestamp in ISO 8601.",
+          "type": "string"
+        },
+        "git_remote_url": {
+          "description": "Stored git remote URL, or null.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name": {
+          "description": "Workspace name as stored.",
+          "type": "string"
+        },
+        "organization_id": {
+          "description": "Organization the workspace was created under.",
+          "type": "string"
+        },
+        "workspace_id": {
+          "description": "UUID of the new workspace. Pass it to pathrule_setup next.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "workspace_id",
+        "name",
+        "organization_id",
+        "git_remote_url",
+        "active_agent_targets",
+        "created_at"
+      ],
+      "type": "object"
+    },
+    "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"
+    },
+    "local_runtime": {
+      "additionalProperties": true,
+      "description": "Present on tools that carry the local-runtime upgrade reminder.",
+      "properties": {
+        "cta": {
+          "description": "Upgrade line to surface to the user when local Pathrule (Studio or CLI) would serve them better than Remote MCP.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "cta"
+      ],
+      "type": "object"
+    },
+    "next_step": {
+      "description": "The call to make next, as { tool, arguments }."
+    },
+    "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"
+}

Changed1 schema field changedJun 9, 2026

changedInput schema / properties / active_agent_targets / items / enum

Previous value: -[
-  "claude-code",
-  "cursor",
-  "windsurf",
-  "codex"
-]New value: +[
+  "claude-code",
+  "cursor",
+  "windsurf",
+  "codex",
+  "copilot"
+]

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 (readOnlyHint=false, destructiveHint=false), the description discloses side effects: it writes the workspace row via JWT, enforces organization membership through RLS, and has no local side effects. It clarifies the scope of creation so an agent won't assume workspace setup is complete.

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 sentences: first states the core action, second lists exclusions with the required alternative, third gives the next step. Every sentence earns its place and is front-loaded, with the most important information appearing first.

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 flat 4-parameter create operation with a full schema and an output schema, the description covers prerequisites (organization membership), side-effect boundaries, and the immediate follow-up call. Nothing essential is missing for an agent to invoke it correctly.

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 the baseline is 3. The description adds context about the workspace_id being returned for pathrule_setup, but the input schema already fully documents each parameter's meaning and constraints. No parameter-level details need to be compensated.

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 and resource: "Create a new Pathrule workspace inside an organization." It immediately distinguishes itself from setup tooling by noting what it does NOT do (attach folder, install client config, render companion files) and names the follow-up sibling pathrule_setup.

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?

The description states when to use this tool (cloud-only creation, with JWT/RLS enforcement), what it does not do (no local attach, no config install), and explicitly routes the agent to call pathrule_setup afterward. This gives clear usage context and exclusions without needing to inspect sibling tools.

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?