Skip to main content
Glama

Pathrule

by io.pathrule

Read Memory

pathrule_read_memory
Read-only

Read the full body and metadata for one Pathrule memory. Use this after pathrule_get_context, pathrule_goto, or pathrule_list_memories returns a memory_id. This reads cloud data only and does not inspect the user's local filesystem.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memory_idYesMemory UUID returned by pathrule_get_context, pathrule_goto, or pathrule_list_memories.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoMemory UUID.
okYestrue when the call succeeded. false when it did not, in which case `error` carries the reason and the success fields are absent.
errorNoPresent only when ok is false.
titleNoMemory title.
sourceNoHow the memory was authored, for example claude or manual.
contentNoFull memory body.
node_pathNoWorkspace-relative path of the node this memory hangs on.
updated_atNoLast update timestamp in ISO 8601.
version_idNoOptimistic-concurrency token. Pass it as expected_version_id to pathrule_update_memory.

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": {
+    "content": {
+      "description": "Full memory body.",
+      "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": "Memory UUID.",
+      "type": "string"
+    },
+    "node_path": {
+      "description": "Workspace-relative path of the node this memory hangs on.",
+      "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": "How the memory was authored, for example claude or manual.",
+      "type": "string"
+    },
+    "title": {
+      "description": "Memory title.",
+      "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_memory.",
+      "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, covering the safety profile. The description adds meaningful behavioral context beyond the annotations: 'reads cloud data only and does not inspect the user's local filesystem,' which clarifies the data source scope, and 'full body and metadata,' which previews the read depth. No contradiction with annotations exists.

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, each earning its place: the core action, the trigger condition naming the source tools, and a scope caveat. The verb+resource is front-loaded and there is zero filler or redundancy.

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 single-parameter read tool with annotations covering the safety profile and an output schema documenting the return shape, the description is complete. It covers what is read, when to call it, where the input comes from, and the cloud-only scope. Nothing an agent needs to invoke it correctly is missing.

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%: the memory_id parameter already documents that it is the UUID returned by pathrule_get_context, pathrule_goto, or pathrule_list_memories. The description reinforces this provenance and adds that it grants access to the 'full body and metadata,' but this is marginal value beyond the schema. Baseline 3 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 states a specific verb ('Read'), resource ('one Pathrule memory'), and scope ('full body and metadata'), which distinguishes it from the sibling read tools (read_rule, read_skill, read_snapshot) and from the memory-producing tools (get_context, goto, list_memories). An agent can immediately tell what this tool does and what it is not.

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 gives explicit when-to-use guidance: 'Use this after pathrule_get_context, pathrule_goto, or pathrule_list_memories returns a memory_id.' This names the exact trigger condition and the sibling tools that produce the required input. It does not explicitly state exclusions or route to alternatives for other cases, but the primary usage condition 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 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