Pathrule

Official

by pathrule

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Pathrule Update Rule

pathrule_update_rule

Destructive

Update a rule's name, content, scope, priority, or move its path. Uses optimistic concurrency to avoid overwriting concurrent changes.

Instructions

Update a rule's fields and/or path. Optimistic concurrency via expected_version_id. Cloud-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace_id": "<workspace_id>",
      "rule_id": "<rule_id>",
      "patch": "<patch>"
    },
    "name": "pathrule_update_rule"
  }
}

Input Schema

Name	Required	Description
`workspace_id`	Yes	Workspace UUID from pathrule_list_workspaces.
`rule_id`	Yes	Rule UUID returned by pathrule_get_context, pathrule_goto, or pathrule_read_rule.
`expected_version_id`	No	Optional optimistic-concurrency token from the existing record. Pass it when available to avoid overwriting a newer edit.
`patch`	Yes
`move_to_path`	No	Optional workspace-relative destination path such as /packages/app. Missing nodes are created when allowed by the backend.
`allow_duplicate`	No	Set true only when intentionally allowing another rule with the same name.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv1.0.4May 27, 2026

addedInput schema / properties / allow_duplicate / description

Added value: +"Set true only when intentionally allowing another rule with the same name."

addedInput schema / properties / expected_version_id / description

Added value: +"Optional optimistic-concurrency token from the existing record. Pass it when available to avoid overwriting a newer edit."

addedInput schema / properties / move_to_path / description

Added value: +"Optional workspace-relative destination path such as /packages/app. Missing nodes are created when allowed by the backend."

addedInput schema / properties / patch / properties / content / description
```
Added value: +"Replacement rule body."
```
addedInput schema / properties / patch / properties / name / description
```
Added value: +"Replacement rule name."
```

addedInput schema / properties / patch / properties / priority / description

Added value: +"Updated priority. Use high only when violating the rule causes real regressions."

addedInput schema / properties / patch / properties / scope_type / description
```
Added value: +"Updated rule scope: project, folder, or file_type."
```

addedInput schema / properties / rule_id / description

Added value: +"Rule UUID returned by pathrule_get_context, pathrule_goto, or pathrule_read_rule."

addedInput schema / properties / workspace_id / description

Added value: +"Workspace UUID from pathrule_list_workspaces."

First observedv1.0.1May 27, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already indicate destructiveHint=true. The description adds value by mentioning optimistic concurrency and cloud-only, which are not covered by annotations. However, it does not disclose auth requirements or what exactly gets destroyed.

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?

The description is extremely concise at two sentences, front-loading the main action and key behavioral traits. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema is provided, and the description does not explain return values, success/failure behavior, or error conditions. For a tool with complex parameters and a nested object, more context is needed for an agent to fully understand the tool's effects.

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 high (83%), so the baseline is 3. The description adds context for expected_version_id (optimistic concurrency) and the overall purpose of patch and move_to_path, but does not elaborate beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it updates a rule's fields and/or path, distinguishing it from other update tools that target memories or skills. However, it does not explicitly differentiate from sibling update tools beyond naming the resource.

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

Usage Guidelines2/5

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

The description mentions optimistic concurrency via expected_version_id and cloud-only, but lacks guidance on when to use this tool versus other rule-related tools (e.g., delete, read) or when not to use it. No exclusions or alternatives are provided.

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