Pathrule

Read Skill

pathrule_read_skill

Read-only

Read the approved snapshot for one Pathrule skill. Use this after pathrule_get_context, pathrule_goto, or pathrule_get_node returns a skill_id. Returns the cloud SKILL.md content for the AI to follow; it does not install or materialize files locally.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`skill_id`	Yes	Skill UUID returned by pathrule_get_context, pathrule_goto, or pathrule_get_node.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Skill UUID.
`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.
`name`	No	Skill name, as invoked with ::name.
`error`	No	Present only when ok is false.
`source`	No	One of manual, template, or github_ref.
`content`	No	Full SKILL.md body, including its frontmatter.
`node_path`	No	Workspace-relative path the skill is attached to.
`updated_at`	No	Last update timestamp in ISO 8601.
`version_id`	No	Optimistic-concurrency token. Pass it as expected_version_id to pathrule_update_skill.

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": {
+    "content": {
+      "description": "Full SKILL.md body, including its frontmatter.",
+      "type": "string"
+    },
+    "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"
+    },
+    "id": {
+      "description": "Skill UUID.",
+      "type": "string"
+    },
+    "name": {
+      "description": "Skill name, as invoked with ::name.",
+      "type": "string"
+    },
+    "node_path": {
+      "description": "Workspace-relative path the skill is attached to.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "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"
+    },
+    "source": {
+      "description": "One of manual, template, or github_ref.",
+      "type": "string"
+    },
+    "updated_at": {
+      "description": "Last update timestamp in ISO 8601.",
+      "type": "string"
+    },
+    "version_id": {
+      "description": "Optimistic-concurrency token. Pass it as expected_version_id to pathrule_update_skill.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

First observedMay 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already mark it read-only, and the description adds meaningful behavior: it returns cloud SKILL.md content and does not install or materialize local files. This clarifies the non-mutating, fetch-only nature beyond the readOnlyHint.

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 with zero filler; the core action appears immediately, and the side-effect clarification and usage trigger each earn their place.

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?

For a single-parameter read operation with strong annotations, the description fully covers what the agent receives and what side effects are absent. It does not describe error/not-found behavior, but that is not essential for invoking this tool 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?

The sole parameter skill_id is already fully described in the schema with the same provenance info. The description reinforces the source of the ID but adds no new semantic detail, so the schema carries the 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?

States a specific action ('Read'), exact resource ('approved snapshot for one Pathrule skill'), and the returned artifact ('cloud SKILL.md content'), distinguishing it from local materialization and adjacent read/update tools.

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?

Explicitly says to use this after pathrule_get_context, pathrule_goto, or pathrule_get_node returns a skill_id. It does not name the alternative tools to avoid or state when not to use it, but the trigger context is unambiguous.

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?