Skip to main content
Glama

Pathrule

by io.pathrule

Pathrule List Project Snapshots

pathrule_list_snapshots
Read-only

List the most recent project snapshots for a workspace (compact metadata only — no file_tree, no sampled_contents). Use to find which snapshot to read in full. Up to 25 per call, ordered newest first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoDefault 10, max 25.
sourceNoFilter to snapshots taken from a specific Pathrule surface.
workspace_idYesWorkspace UUID from pathrule_list_workspaces.

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.
dataNoSnapshot metadata list. Load one in full with pathrule_read_snapshot.
errorNoPresent only when ok is false.
human_messageNoOne-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.

  1. Changed2 schema fields changed
    • addedInput schema / properties / workspace_id / description
      Added value: +"Workspace UUID from pathrule_list_workspaces."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "description": "Snapshot metadata list. Load one in full with pathrule_read_snapshot.",
+      "properties": {
+        "count": {
+          "description": "Number of snapshots returned.",
+          "type": "number"
+        },
+        "snapshots": {
+          "description": "Newest first. Metadata only: id, source, project_name, git_remote_url, branch, git_head, file_count, total_size_bytes, created_at.",
+          "items": {},
+          "type": "array"
+        },
+        "workspace_id": {
+          "description": "Workspace the snapshots belong to.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "workspace_id",
+        "count",
+        "snapshots"
+      ],
+      "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"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral constraints beyond that: 'Up to 25 per call, ordered newest first' and the guarantee that file_tree and sampled_contents are omitted. This gives the agent accurate expectations without contradicting the annotations.

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 compact sentences deliver the core purpose, exclusions, usage guidance, ordering, and limit without filler. The most decision-relevant information is front-loaded, and every sentence earns its place.

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 tool is a simple list operation with a full output schema and fully documented parameters. The description covers ordering, limit, content scope, and the intended workflow, so an agent has everything needed to select and invoke it 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?

Schema description coverage is 100%, with each parameter already documented: workspace_id is a UUID, limit has a default and max, and source has an enum. The description adds little new parameter-level meaning beyond confirming the workspace scope and the 25-per-call limit, so the baseline of 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?

Description names a specific verb ('List'), a specific resource ('most recent project snapshots for a workspace'), and a precise scope ('compact metadata only — no file_tree, no sampled_contents'). It clearly distinguishes this from pathrule_read_snapshot by framing it as the discovery step before reading a full snapshot.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use the tool: 'Use to find which snapshot to read in full.' The 'compact metadata only — no file_tree, no sampled_contents' exclusion makes clear it is not for retrieving snapshot contents, pointing the agent toward the read-snapshot sibling for full data.

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