drupal-mcp-connector 2.7.4 → 2.8.0

package/{.claude → .agents}/commands/drupal-drush-config-import.md

@@ -1,16 +1,15 @@
 ---
 description: "Import configuration from the sync directory into the database. Requires write access. Confirm with user before running on production."
 argument-hint: "[site]"
-allowed-tools: mcp__drupal__drupal_drush_config_import
 ---
 
-Call the `mcp__drupal__drupal_drush_config_import` MCP tool.
+Call the MCP tool `drupal_drush_config_import`.
 
 Import configuration from the sync directory into the database. Requires write access. Confirm with user before running on production.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Optional:**
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-drush-config-status.md

@@ -1,16 +1,15 @@
 ---
 description: "Check if active config is in sync with the sync directory. Returns out-of-sync items if any."
 argument-hint: "[site]"
-allowed-tools: mcp__drupal__drupal_drush_config_status
 ---
 
-Call the `mcp__drupal__drupal_drush_config_status` MCP tool.
+Call the MCP tool `drupal_drush_config_status`.
 
 Check if active config is in sync with the sync directory. Returns out-of-sync items if any.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Optional:**
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-drush-cron.md

@@ -1,16 +1,15 @@
 ---
 description: "Run Drupal cron via `drush cron`."
 argument-hint: "[site]"
-allowed-tools: mcp__drupal__drupal_drush_cron
 ---
 
-Call the `mcp__drupal__drupal_drush_cron` MCP tool.
+Call the MCP tool `drupal_drush_cron`.
 
 Run Drupal cron via `drush cron`.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Optional:**
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-drush-module-disable.md

@@ -1,16 +1,15 @@
 ---
 description: "Uninstall a Drupal module. Irreversible for module-stored data. Confirm with user."
 argument-hint: "<moduleName> [site]"
-allowed-tools: mcp__drupal__drupal_drush_module_disable
 ---
 
-Call the `mcp__drupal__drupal_drush_module_disable` MCP tool.
+Call the MCP tool `drupal_drush_module_disable`.
 
 Uninstall a Drupal module. Irreversible for module-stored data. Confirm with user.
 
 > ⚠ **Destructive** — this permanently changes or deletes data. Confirm with the user before calling.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Required:**
 - `moduleName` (string)
@@ -18,4 +17,4 @@ Parse the request in `$ARGUMENTS` into this tool's parameters:
 **Optional:**
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-drush-module-enable.md

@@ -1,14 +1,13 @@
 ---
 description: "Enable a Drupal module. Module name validated as machine name. Requires write access."
 argument-hint: "<moduleName> [site]"
-allowed-tools: mcp__drupal__drupal_drush_module_enable
 ---
 
-Call the `mcp__drupal__drupal_drush_module_enable` MCP tool.
+Call the MCP tool `drupal_drush_module_enable`.
 
 Enable a Drupal module. Module name validated as machine name. Requires write access.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Required:**
 - `moduleName` (string)
@@ -16,4 +15,4 @@ Parse the request in `$ARGUMENTS` into this tool's parameters:
 **Optional:**
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-drush-module-list.md

@@ -1,17 +1,16 @@
 ---
 description: "List Drupal modules. Filter by enabled or disabled status."
 argument-hint: "[site] [status]"
-allowed-tools: mcp__drupal__drupal_drush_module_list
 ---
 
-Call the `mcp__drupal__drupal_drush_module_list` MCP tool.
+Call the MCP tool `drupal_drush_module_list`.
 
 List Drupal modules. Filter by enabled or disabled status.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Optional:**
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 - `status` (string)
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-drush-security-updates.md

@@ -1,16 +1,15 @@
 ---
 description: "List modules with known security advisories via `drush pm:security`."
 argument-hint: "[site]"
-allowed-tools: mcp__drupal__drupal_drush_security_updates
 ---
 
-Call the `mcp__drupal__drupal_drush_security_updates` MCP tool.
+Call the MCP tool `drupal_drush_security_updates`.
 
 List modules with known security advisories via `drush pm:security`.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Optional:**
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-drush-sql-query.md

@@ -1,14 +1,13 @@
 ---
 description: "Run a single read-only SELECT through mcp_sentinel's governed command (`drush mcp-sentinel:sql-query`). Requires the site to set drushSsh.rawSql=\"governed\" AND the site's policy profile to set allow_raw_sql; both are off by default. The server refuses statements touching a denied entity type, a non-entity table, or a redacted field, and records every attempt in the tamper-evident audit log. Use the site-context or entity-schema tools for schema introspection."
 argument-hint: "<query> [site]"
-allowed-tools: mcp__drupal__drupal_drush_sql_query
 ---
 
-Call the `mcp__drupal__drupal_drush_sql_query` MCP tool.
+Call the MCP tool `drupal_drush_sql_query`.
 
 Run a single read-only SELECT through mcp_sentinel's governed command (`drush mcp-sentinel:sql-query`). Requires the site to set drushSsh.rawSql="governed" AND the site's policy profile to set allow_raw_sql; both are off by default. The server refuses statements touching a denied entity type, a non-entity table, or a redacted field, and records every attempt in the tamper-evident audit log. Use the site-context or entity-schema tools for schema introspection.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Required:**
 - `query` (string)
@@ -16,4 +15,4 @@ Parse the request in `$ARGUMENTS` into this tool's parameters:
 **Optional:**
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-drush-status.md

@@ -1,16 +1,15 @@
 ---
 description: "Get Drupal site status via `drush status` — version, DB, file paths, active config."
 argument-hint: "[site]"
-allowed-tools: mcp__drupal__drupal_drush_status
 ---
 
-Call the `mcp__drupal__drupal_drush_status` MCP tool.
+Call the MCP tool `drupal_drush_status`.
 
 Get Drupal site status via `drush status` — version, DB, file paths, active config.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Optional:**
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-drush-updatedb.md

@@ -1,16 +1,15 @@
 ---
 description: "Run pending database updates via `drush updatedb`. Always run after deploying module updates."
 argument-hint: "[site]"
-allowed-tools: mcp__drupal__drupal_drush_updatedb
 ---
 
-Call the `mcp__drupal__drupal_drush_updatedb` MCP tool.
+Call the MCP tool `drupal_drush_updatedb`.
 
 Run pending database updates via `drush updatedb`. Always run after deploying module updates.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Optional:**
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-drush-user-create.md

@@ -1,14 +1,13 @@
 ---
 description: "Create a Drupal user and optionally assign roles. Requires write access."
 argument-hint: "<name> <mail> <password> [site] [roles]"
-allowed-tools: mcp__drupal__drupal_drush_user_create
 ---
 
-Call the `mcp__drupal__drupal_drush_user_create` MCP tool.
+Call the MCP tool `drupal_drush_user_create`.
 
 Create a Drupal user and optionally assign roles. Requires write access.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Required:**
 - `name` (string)
@@ -19,4 +18,4 @@ Parse the request in `$ARGUMENTS` into this tool's parameters:
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 - `roles` (array (pass as JSON))
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-drush-user-list.md

@@ -1,14 +1,13 @@
 ---
 description: "List Drupal users via Drush. Filter by active/blocked status or role."
 argument-hint: "[site] [status] [role] [limit]"
-allowed-tools: mcp__drupal__drupal_drush_user_list
 ---
 
-Call the `mcp__drupal__drupal_drush_user_list` MCP tool.
+Call the MCP tool `drupal_drush_user_list`.
 
 List Drupal users via Drush. Filter by active/blocked status or role.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Optional:**
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
@@ -16,4 +15,4 @@ Parse the request in `$ARGUMENTS` into this tool's parameters:
 - `role` (string)
 - `limit` (number)
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-drush-watchdog.md

@@ -1,14 +1,13 @@
 ---
 description: "Fetch recent Drupal watchdog/dblog entries. Filter by type or severity level."
 argument-hint: "[site] [type] [severity] [limit]"
-allowed-tools: mcp__drupal__drupal_drush_watchdog
 ---
 
-Call the `mcp__drupal__drupal_drush_watchdog` MCP tool.
+Call the MCP tool `drupal_drush_watchdog`.
 
 Fetch recent Drupal watchdog/dblog entries. Filter by type or severity level.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Optional:**
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
@@ -16,4 +15,4 @@ Parse the request in `$ARGUMENTS` into this tool's parameters:
 - `severity` (string)
 - `limit` (number)
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-entity-create.md

@@ -1,14 +1,13 @@
 ---
 description: "Create an entity of any Drupal entity type and bundle. Use drupal_get_entity_schema first to know what fields are available. All operations checked against security config."
 argument-hint: "<entityType> <bundle> [site] [attributes] [relationships] [dryRun] [returning]"
-allowed-tools: mcp__drupal__drupal_entity_create
 ---
 
-Call the `mcp__drupal__drupal_entity_create` MCP tool.
+Call the MCP tool `drupal_entity_create`.
 
 Create an entity of any Drupal entity type and bundle. Use drupal_get_entity_schema first to know what fields are available. All operations checked against security config.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Required:**
 - `entityType` (string)
@@ -21,4 +20,4 @@ Parse the request in `$ARGUMENTS` into this tool's parameters:
 - `dryRun` (boolean (true/false)): Validate and return a preview of the create without committing.
 - `returning` (string): Response verbosity. "full" (default) returns the complete saved entity; "minimal" returns just identity + state (id, type, bundle, title, status, changed, url) — much smaller, recommended for bulk writes where the echoed body would dominate the response.
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-entity-delete.md

@@ -1,16 +1,15 @@
 ---
 description: "Delete an entity of any Drupal entity type. Requires allowDestructive = true in security config. Confirm with the user before calling."
 argument-hint: "<entityType> <bundle> <id> [site] [dryRun]"
-allowed-tools: mcp__drupal__drupal_entity_delete
 ---
 
-Call the `mcp__drupal__drupal_entity_delete` MCP tool.
+Call the MCP tool `drupal_entity_delete`.
 
 Delete an entity of any Drupal entity type. Requires allowDestructive = true in security config. Confirm with the user before calling.
 
 > ⚠ **Destructive** — this permanently changes or deletes data. Confirm with the user before calling.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Required:**
 - `entityType` (string)
@@ -21,4 +20,4 @@ Parse the request in `$ARGUMENTS` into this tool's parameters:
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 - `dryRun` (boolean (true/false)): Validate and return a preview of the delete without committing.
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-entity-get.md

@@ -1,14 +1,13 @@
 ---
 description: "Fetch a single entity of any Drupal entity type by UUID."
 argument-hint: "<entityType> <bundle> <id> [site] [include]"
-allowed-tools: mcp__drupal__drupal_entity_get
 ---
 
-Call the `mcp__drupal__drupal_entity_get` MCP tool.
+Call the MCP tool `drupal_entity_get`.
 
 Fetch a single entity of any Drupal entity type by UUID.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Required:**
 - `entityType` (string)
@@ -19,4 +18,4 @@ Parse the request in `$ARGUMENTS` into this tool's parameters:
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 - `include` (array (pass as JSON)): Relationship field names to sideload
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-entity-list.md

@@ -1,14 +1,13 @@
 ---
 description: "List entities of any Drupal entity type and bundle. Supports structured filters, sorting, pagination, and relationship includes. Use drupal_list_entity_types first to discover available types."
 argument-hint: "<entityType> <bundle> [site] [filters] [sort] [include] [limit] [offset]"
-allowed-tools: mcp__drupal__drupal_entity_list
 ---
 
-Call the `mcp__drupal__drupal_entity_list` MCP tool.
+Call the MCP tool `drupal_entity_list`.
 
 List entities of any Drupal entity type and bundle. Supports structured filters, sorting, pagination, and relationship includes. Use drupal_list_entity_types first to discover available types.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Required:**
 - `entityType` (string): Entity type machine name, e.g. 'paragraph', 'block_content', 'commerce_product'
@@ -22,4 +21,4 @@ Parse the request in `$ARGUMENTS` into this tool's parameters:
 - `limit` (number)
 - `offset` (number)
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-entity-update.md

@@ -1,14 +1,13 @@
 ---
-description: "Update an existing entity of any Drupal entity type. Only include attributes/relationships you want to change. Published moderated targets without an explicit attributes.moderation_state default to moderation_state 'draft' (forward revision). Paragraph / ERR identifiers are resolved to include meta.target_revision_id before PATCH; the write fails if any ref cannot be resolved. On moderated targets an id-mismatch PATCH preflight runs first (including dryRun) so a core working-copy guard failure is reported before the real write and no revision is saved by the probe (#201). Preflight does not un-orphan paragraphs already created — probe the host before creating dependents."
+description: "Update an existing entity of any Drupal entity type. Only include attributes/relationships you want to change. Published moderated targets without an explicit attributes.moderation_state default to moderation_state 'draft' (forward revision). Paragraph / ERR identifiers are resolved to include meta.target_revision_id before PATCH; the write fails if any ref cannot be resolved. On moderated targets an id-mismatch PATCH preflight runs first (including dryRun) against the same URL the write will hit. An addressable working copy is PATCHed via ?resourceVersion=rel:working-copy (#166); a stray revision with no addressable working copy still fails with revision-surgery language (#201). Preflight does not un-orphan paragraphs already created — probe the host before creating dependents."
 argument-hint: "<entityType> <bundle> <id> [site] [attributes] [relationships] [dryRun] [returning]"
-allowed-tools: mcp__drupal__drupal_entity_update
 ---
 
-Call the `mcp__drupal__drupal_entity_update` MCP tool.
+Call the MCP tool `drupal_entity_update`.
 
-Update an existing entity of any Drupal entity type. Only include attributes/relationships you want to change. Published moderated targets without an explicit attributes.moderation_state default to moderation_state 'draft' (forward revision). Paragraph / ERR identifiers are resolved to include meta.target_revision_id before PATCH; the write fails if any ref cannot be resolved. On moderated targets an id-mismatch PATCH preflight runs first (including dryRun) so a core working-copy guard failure is reported before the real write and no revision is saved by the probe (#201). Preflight does not un-orphan paragraphs already created — probe the host before creating dependents.
+Update an existing entity of any Drupal entity type. Only include attributes/relationships you want to change. Published moderated targets without an explicit attributes.moderation_state default to moderation_state 'draft' (forward revision). Paragraph / ERR identifiers are resolved to include meta.target_revision_id before PATCH; the write fails if any ref cannot be resolved. On moderated targets an id-mismatch PATCH preflight runs first (including dryRun) against the same URL the write will hit. An addressable working copy is PATCHed via ?resourceVersion=rel:working-copy (#166); a stray revision with no addressable working copy still fails with revision-surgery language (#201). Preflight does not un-orphan paragraphs already created — probe the host before creating dependents.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Required:**
 - `entityType` (string)
@@ -19,7 +18,7 @@ Parse the request in `$ARGUMENTS` into this tool's parameters:
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 - `attributes` (object (pass as JSON))
 - `relationships` (object (pass as JSON))
-- `dryRun` (boolean (true/false)): Validate, resolve ERR identifiers, and (on moderated targets) run the core PATCH-guard probe against Drupal, then return a preview without the real write. The probe uses a non-matching data.id so Drupal does not save. A working-copy 400 fails the dryRun.
+- `dryRun` (boolean (true/false)): Validate, resolve ERR identifiers, and (on moderated targets) run the core PATCH-guard probe against Drupal, then return a preview without the real write. The probe uses a non-matching data.id so Drupal does not save, and hits the same URL as the real write (canonical, or ?resourceVersion=rel:working-copy when a draft is addressable). A working-copy 400 fails the dryRun.
 - `returning` (string): Response verbosity. "full" (default) returns the complete saved entity; "minimal" returns just identity + state (id, type, bundle, title, status, changed, url) — much smaller, recommended for bulk writes where the echoed body would dominate the response.
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-find-orphaned-media.md

@@ -1,18 +1,17 @@
 ---
 description: "Find media entities not referenced by any content. Useful for storage cleanup audits."
 argument-hint: "[site] [type] [limit]"
-allowed-tools: mcp__drupal__drupal_find_orphaned_media
 ---
 
-Call the `mcp__drupal__drupal_find_orphaned_media` MCP tool.
+Call the MCP tool `drupal_find_orphaned_media`.
 
 Find media entities not referenced by any content. Useful for storage cleanup audits.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Optional:**
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 - `type` (string): Media type to check (default: image)
 - `limit` (number)
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-get-entity-schema.md

@@ -1,14 +1,13 @@
 ---
 description: "Inspect the fields and relationships available on any Drupal entity type + bundle. Run this before creating or updating entities to know what fields are available."
 argument-hint: "<entityType> <bundle> [site]"
-allowed-tools: mcp__drupal__drupal_get_entity_schema
 ---
 
-Call the `mcp__drupal__drupal_get_entity_schema` MCP tool.
+Call the MCP tool `drupal_get_entity_schema`.
 
 Inspect the fields and relationships available on any Drupal entity type + bundle. Run this before creating or updating entities to know what fields are available.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Required:**
 - `entityType` (string): e.g. 'node', 'paragraph', 'commerce_product', 'block_content'
@@ -17,4 +16,4 @@ Parse the request in `$ARGUMENTS` into this tool's parameters:
 **Optional:**
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-get-media.md

@@ -1,14 +1,13 @@
 ---
 description: "Fetch a single media entity by UUID and media type."
 argument-hint: "<type> <id> [site]"
-allowed-tools: mcp__drupal__drupal_get_media
 ---
 
-Call the `mcp__drupal__drupal_get_media` MCP tool.
+Call the MCP tool `drupal_get_media`.
 
 Fetch a single media entity by UUID and media type.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Required:**
 - `type` (string)
@@ -17,4 +16,4 @@ Parse the request in `$ARGUMENTS` into this tool's parameters:
 **Optional:**
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-get-node.md

@@ -1,14 +1,13 @@
 ---
 description: "Fetch a single Drupal content node by UUID and content type. Returns title, body, status, path alias, and all attributes."
 argument-hint: "<type> <id> [site]"
-allowed-tools: mcp__drupal__drupal_get_node
 ---
 
-Call the `mcp__drupal__drupal_get_node` MCP tool.
+Call the MCP tool `drupal_get_node`.
 
 Fetch a single Drupal content node by UUID and content type. Returns title, body, status, path alias, and all attributes.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Required:**
 - `type` (string): Content type machine name, e.g. 'article'
@@ -17,4 +16,4 @@ Parse the request in `$ARGUMENTS` into this tool's parameters:
 **Optional:**
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-get-paragraph.md

@@ -1,14 +1,13 @@
 ---
 description: "Fetch a single Paragraph entity by paragraph type (bundle) and UUID. Returns the redacted paragraph (fields include drupal_internal__revision_id) plus a `ref` ({ type: 'paragraph--<bundle>', id, meta: { target_revision_id } }) you can use to embed it in a host entity's paragraph / ERR field. Paragraphs are referenced from a host field rather than queried standalone in production. Governed by the site security policy."
 argument-hint: "<paragraphType> <id> [site]"
-allowed-tools: mcp__drupal__drupal_get_paragraph
 ---
 
-Call the `mcp__drupal__drupal_get_paragraph` MCP tool.
+Call the MCP tool `drupal_get_paragraph`.
 
 Fetch a single Paragraph entity by paragraph type (bundle) and UUID. Returns the redacted paragraph (fields include drupal_internal__revision_id) plus a `ref` ({ type: 'paragraph--<bundle>', id, meta: { target_revision_id } }) you can use to embed it in a host entity's paragraph / ERR field. Paragraphs are referenced from a host field rather than queried standalone in production. Governed by the site security policy.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Required:**
 - `paragraphType` (string): Paragraph type / bundle machine name
@@ -17,4 +16,4 @@ Parse the request in `$ARGUMENTS` into this tool's parameters:
 **Optional:**
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-get-revision.md

@@ -1,14 +1,13 @@
 ---
 description: "Fetch a single revision of a content node by version id or alias. `version` may be a numeric vid (e.g. 42), an explicit 'id:<vid>', or the relative aliases 'rel:latest-version' / 'rel:working-copy'. Read-only; attributes are redacted per security policy."
 argument-hint: "<type> <id> <version> [site]"
-allowed-tools: mcp__drupal__drupal_get_revision
 ---
 
-Call the `mcp__drupal__drupal_get_revision` MCP tool.
+Call the MCP tool `drupal_get_revision`.
 
 Fetch a single revision of a content node by version id or alias. `version` may be a numeric vid (e.g. 42), an explicit 'id:<vid>', or the relative aliases 'rel:latest-version' / 'rel:working-copy'. Read-only; attributes are redacted per security policy.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Required:**
 - `type` (string): Content type machine name
@@ -18,4 +17,4 @@ Parse the request in `$ARGUMENTS` into this tool's parameters:
 **Optional:**
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.

package/{.claude → .agents}/commands/drupal-get-taxonomy-term.md

@@ -1,14 +1,13 @@
 ---
 description: "Fetch a single taxonomy term by UUID."
 argument-hint: "<vocabulary> <id> [site]"
-allowed-tools: mcp__drupal__drupal_get_taxonomy_term
 ---
 
-Call the `mcp__drupal__drupal_get_taxonomy_term` MCP tool.
+Call the MCP tool `drupal_get_taxonomy_term`.
 
 Fetch a single taxonomy term by UUID.
 
-Parse the request in `$ARGUMENTS` into this tool's parameters:
+Parse the arguments supplied with this command into this tool's parameters:
 
 **Required:**
 - `vocabulary` (string)
@@ -17,4 +16,4 @@ Parse the request in `$ARGUMENTS` into this tool's parameters:
 **Optional:**
 - `site` (string): Named site from connector config. Omit only on reads: multi-site configs fall back to defaultSite (often local/dev, not production). Writes require an explicit site when more than one site is configured. Every response includes `_target` { name, baseUrl, source } (`hint` when you passed site, `default` when you did not).
 
-If a required parameter is missing from `$ARGUMENTS`, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.
+If a required parameter is missing, ask before calling — do not invent values. Coerce each value to its JSON type (booleans → true/false, numbers → numeric, object/array → parse JSON), then make the single tool call and summarize the result.