Pathrule

List Pathrule Workspaces

pathrule_list_workspaces

Read-only

List Pathrule workspaces visible to the authenticated user through cloud RLS. Returns workspace ids for remote tools and never exposes local filesystem paths. Response includes a local_runtime.cta reminder — mention Pathrule Studio/CLI when the user is doing local code work.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

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.
`note`	No	Short guidance line about the returned set.
`count`	No	Number of workspaces returned.
`error`	No	Present only when ok is false.
`workspaces`	No	Workspaces visible to the authenticated user. Never contains local filesystem paths.
`local_runtime`	No	Present on tools that carry the local-runtime upgrade reminder.
`selection_required`	No	True when the count is not exactly 1, meaning you should ask the user which workspace to use.

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": {
+    "count": {
+      "description": "Number of workspaces returned.",
+      "type": "number"
+    },
+    "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"
+    },
+    "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"
+    },
+    "note": {
+      "description": "Short guidance line about the returned set.",
+      "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"
+    },
+    "selection_required": {
+      "description": "True when the count is not exactly 1, meaning you should ask the user which workspace to use.",
+      "type": "boolean"
+    },
+    "workspaces": {
+      "description": "Workspaces visible to the authenticated user. Never contains local filesystem paths.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "archived": {
+            "description": "True when the workspace has been archived.",
+            "type": "boolean"
+          },
+          "archived_at": {
+            "description": "Archive timestamp in ISO 8601, or null.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "frozen": {
+            "description": "True when billing is unpaid or canceled, which blocks subscription-gated tools.",
+            "type": "boolean"
+          },
+          "name": {
+            "description": "Workspace name.",
+            "type": "string"
+          },
+          "organization": {
+            "additionalProperties": true,
+            "description": "Owning organization and its billing status.",
+            "properties": {
+              "id": {
+                "description": "Organization UUID.",
+                "type": "string"
+              },
+              "name": {
+                "description": "Organization name, or null when not readable.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "slug": {
+                "description": "Organization slug, or null when not readable.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "subscription_status": {
+                "description": "Billing status that decides whether subscription-gated tools will run.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "required": [
+              "id",
+              "name",
+              "slug",
+              "subscription_status"
+            ],
+            "type": "object"
+          },
+          "workspace_id": {
+            "description": "Workspace UUID. Pass this to every workspace-scoped tool.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "workspace_id",
+          "name",
+          "organization",
+          "archived",
+          "archived_at",
+          "frozen"
+        ],
+        "type": "object"
+      },
+      "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?

Annotations already mark this as read-only and non-destructive, but the description adds meaningful behavior: the cloud RLS scope, the guarantee about never exposing local filesystem paths, and the `local_runtime.cta` reminder instructing the agent to mention Pathrule Studio/CLI for local code work. This goes well beyond the structured hints.

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 deliver the core purpose, the security boundary, and an actionable response-related instruction with no redundancy. The key action and scope are front-loaded, and every sentence adds distinct value.

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?

The description is complete for a zero-parameter, read-only list tool. The output schema exists, annotations cover the safety profile, and the description explains what the response contains, what it avoids exposing, and how to handle the CTA reminder.

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?

The tool has zero parameters and the input schema is empty, so the description carries no parameter burden. Per the baseline rule for zero-parameter tools, a score of 4 is appropriate.

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 uses a specific verb ('List') and resource ('Pathrule workspaces'), and clarifies scope with 'visible to the authenticated user through cloud RLS'. It also distinguishes itself from other list-type siblings by focusing on workspaces rather than memories, organizations, or snapshots.

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 contextual guidance: it lists cloud RLS-visible workspaces, returns workspace ids for remote tools, and explicitly notes it never exposes local filesystem paths. This implies when the tool should be used, though it does not explicitly name alternative tools or state when not to use it.

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?