Skip to main content
Glama

Pathrule

by io.pathrule

Pathrule Cloud Ping

pathrule_ping
Read-only

Sanity check that Pathrule Remote MCP is reachable. Cloud-safe: returns no local cwd. Response includes a local_runtime.cta line you can surface to the user when they ask about deeper Pathrule features.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageNoOptional message to echo back.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYestrue when the call succeeded. false when it did not, in which case `error` carries the reason and the success fields are absent.
tsNoServer timestamp in ISO 8601.
echoNoThe `message` argument echoed back, or null when none was sent.
pongNoPresent and true when the endpoint answered.
cloudNoAlways true on Remote MCP. Marks the response as cloud-served, with no local cwd.
errorNoPresent only when ok is false.
versionNoConnector build identifier.
client_idNoOAuth client id of the calling MCP client, or null on an unauthenticated ping.
authenticatedNoPresent and false only on the unauthenticated public ping.
local_runtimeNoPresent on tools that carry the local-runtime upgrade reminder.

Schema Changelog

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

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "authenticated": {
+      "description": "Present and false only on the unauthenticated public ping.",
+      "type": "boolean"
+    },
+    "client_id": {
+      "description": "OAuth client id of the calling MCP client, or null on an unauthenticated ping.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "cloud": {
+      "description": "Always true on Remote MCP. Marks the response as cloud-served, with no local cwd.",
+      "type": "boolean"
+    },
+    "echo": {
+      "description": "The `message` argument echoed back, or null when none was sent.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "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"
+    },
+    "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"
+    },
+    "pong": {
+      "const": true,
+      "description": "Present and true when the endpoint answered.",
+      "type": "boolean"
+    },
+    "ts": {
+      "description": "Server timestamp in ISO 8601.",
+      "type": "string"
+    },
+    "version": {
+      "description": "Connector build identifier.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral context: it is cloud-safe, returns no local cwd, and includes a local_runtime.cta line in the response. This goes beyond the structured annotations without contradicting them.

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?

Two sentences, each earning its place. The purpose is front-loaded, and the second sentence adds valuable behavioral and user-guidance context without unnecessary detail.

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 simple one-optional-parameter, read-only ping tool with an output schema and strong annotations, the description is complete enough. It covers purpose, safety, and an important response element an agent might surface to users.

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 optional message parameter is already documented in the schema. The description does not add parameter-specific semantics, but the baseline of 3 applies because the schema carries the full burden.

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 and resource: 'Sanity check that Pathrule Remote MCP is reachable.' It clearly identifies this as a connectivity probe and distinguishes it from the many sibling tools that manage workspaces, memories, rules, 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 implies when to use it: when you need to verify that Pathrule Remote MCP is reachable. It also adds the cloud-safety note ('returns no local cwd') and hints at surfacing the CTA line for deeper-feature questions. It does not explicitly name alternatives or exclusions, but no sibling tool serves the same ping purpose.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Pathrule toolsInspect
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