Pathrule

Get Local Runtime Upgrade

pathrule_get_local_runtime_upgrade

Read-only

Explain what Pathrule CLI (power-user, terminal-first) and Pathrule Studio (GUI) unlock beyond Remote MCP. Call this when the user asks 'is there a better way?', 'why do I need to install something?', wants hook-level automation, or wants to compare surfaces. The response splits the pitch by audience (CLI for terminal-first, Pathrule Studio for GUI) and explains the real token-savings angle: hooks fire before every AI tool call and inject context for free, while remote MCP is manual mode where the AI spends tokens on each context fetch.

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.
`data`	No	Surface comparison split by audience.
`error`	No	Present only when ok is false.
`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,
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "description": "Surface comparison split by audience.",
+      "properties": {
+        "cloud_connector_can": {
+          "description": "What Remote MCP alone can already do.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "cta": {
+          "additionalProperties": true,
+          "description": "Where to send a user who wants the local runtime.",
+          "properties": {
+            "label": {
+              "description": "Call-to-action label.",
+              "type": "string"
+            },
+            "message": {
+              "description": "One-line upgrade message to relay to the user.",
+              "type": "string"
+            },
+            "url": {
+              "description": "Download page URL.",
+              "type": "string"
+            }
+          },
+          "required": [
+            "label",
+            "url",
+            "message"
+          ],
+          "type": "object"
+        },
+        "for_fast_gui_users_desktop": {
+          "description": "Pitch for GUI users (Pathrule Studio)."
+        },
+        "for_power_users_cli_plus_web": {
+          "description": "Pitch for terminal-first users (Pathrule CLI)."
+        },
+        "remote_mcp_stays_useful_for": {
+          "description": "Cases where Remote MCP remains the right surface."
+        },
+        "why_upgrade": {
+          "description": "The token-cost argument for a local runtime."
+        }
+      },
+      "required": [
+        "cloud_connector_can",
+        "cta"
+      ],
+      "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"
+    },
+    "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

A4.4/5.0

Behavior4/5

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

Annotations already mark the tool read-only and non-destructive; the description adds useful behavioral detail by disclosing that the response is a side-by-side pitch split by audience and that it emphasizes the token-savings mechanism of hooks versus manual remote MCP. No contradiction with annotations.

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

Conciseness4/5

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

The description is front-loaded with its core purpose and the usage triggers are placed early. The final sentence is somewhat long and partially restates the CLI/Studio audience split, but each sentence still contributes actionable information.

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 zero-parameter, read-only explainer with an output schema, the description covers what the tool does, when to invoke it, and what the response will contain. Nothing essential is missing for correct selection and use.

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?

There are zero parameters and an empty schema, so there is no parameter ambiguity for the description to resolve. The baseline of 4 applies because the description correctly avoids inventing parameter guidance.

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 states a specific communicative action ('Explain what Pathrule CLI and Pathrule Studio unlock beyond Remote MCP') and differentiates this tool from the sibling data-retrieval and mutation tools by making it an audience-targeted explanation rather than a resource operation. The triggers and response focus make the tool's unique 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?

It gives explicit call conditions ('Call this when the user asks...') and concrete user intents such as wanting hook-level automation or comparing surfaces. It does not explicitly say when not to use specific sibling tools, but the trigger framing is enough to route an agent correctly.

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?