Update microagent documentation to clarify that type field is optional

Co-authored-by: Engel Nyst <enyst@users.noreply.github.com>

docs/usage/prompting/microagents-keyword.mdx

@@ -5,26 +5,111 @@ description: Keyword-triggered microagents provide OpenHands with specific instr
 
 ## Usage
 
-These microagents are only loaded when a prompt includes one of the trigger words.
+Keyword-triggered microagents are only loaded when a prompt includes one of the trigger words. There are two types of keyword-triggered microagents:
+
+1. **Standard Keyword Microagents**: Triggered by keywords embedded in text
+2. **Command-Style Microagents**: Triggered by command-style inputs (e.g., `/fix_test`) that can prompt for user input
+
+Additionally, there's a special type of microagent that's always active:
+
+3. **Repository Microagents**: Always active for a specific repository, providing repository-specific context and tools
 
 ## Frontmatter Syntax
 
 Frontmatter is required for keyword-triggered microagents. It must be placed at the top of the file,
-above the guidelines.
+above the guidelines. Enclose the frontmatter in triple dashes (---).
 
-Enclose the frontmatter in triple dashes (---) and include the following fields:
+### Standard Keyword Microagents
+
+For standard keyword microagents, include the following fields:
 
 | Field      | Description                                      | Required | Default          |
 |------------|--------------------------------------------------|----------|------------------|
+| `name`     | The name of the microagent                       | No       | Filename         |
+| `type`     | The type of microagent (`knowledge`)             | No       | Inferred         |
 | `triggers` | A list of keywords that activate the microagent. | Yes      | None             |
-| `agent`    | The agent this microagent applies to.            | No       | 'CodeActAgent'   |
 
+### Command-Style Microagents
 
-## Example
+For command-style microagents that require user input, include the following fields:
 
-Keyword-triggered microagent file example located at `.openhands/microagents/yummy.md`:
-```
+| Field      | Description                                                | Required | Default          |
+|------------|------------------------------------------------------------|----------|------------------|
+| `name`     | The name of the microagent                                 | No       | Filename         |
+| `type`     | The type of microagent (`task`)                            | No       | Inferred         |
+| `triggers` | A list of command triggers (e.g., `/fix_test`)             | No       | `/[name]`        |
+| `inputs`   | A list of input variables the microagent requires          | Yes      | None             |
+
+### Repository Microagents
+
+Repository microagents are always active for a specific repository. They provide repository-specific context and tools.
+
+| Field      | Description                                                | Required | Default          |
+|------------|------------------------------------------------------------|----------|------------------|
+| `name`     | The name of the microagent                                 | No       | Filename         |
+| `type`     | The type of microagent (`repo`)                            | No       | Inferred         |
+
+#### Repository Microagent Example
+
+Here's an example of a repository microagent:
+
+```yaml
 ---
+# The type field is optional and will be inferred as 'repo' when no triggers are present
+---
+
+# Repository Guidelines
+
+This repository follows these coding standards:
+1. Use PEP 8 for Python code
+2. Use ESLint for JavaScript code
+3. Write unit tests for all new features
+```
+
+This microagent is always active when working with the repository and provides repository-specific guidelines.
+
+### MCP Tools Support
+
+Microagents can also provide additional MCP (Model-Code-Prompt) tools to the agent. This is useful for extending the agent's capabilities with custom tools.
+
+| Field        | Description                                                | Required | Default          |
+|--------------|-----------------------------------------------------------|----------|------------------|
+| `mcp_tools`  | Configuration for additional MCP tools                     | No       | None             |
+
+#### MCP Tools Example
+
+Here's an example of a microagent that provides an additional MCP tool (the `fetch` tool for accessing web content):
+
+```yaml
+---
+# The type field is optional and will be inferred as 'repo' when no triggers are present
+mcp_tools:
+  stdio_servers:
+    - name: "fetch"
+      command: uvx
+      args:
+        - mcp-server-fetch
+---
+```
+
+This microagent is a repository microagent (always active) that adds the `fetch` tool to the agent's capabilities.
+
+Each input in the `inputs` list requires:
+
+| Field         | Description                                      | Required |
+|---------------|--------------------------------------------------|----------|
+| `name`        | The name of the input variable                   | Yes      |
+| `description` | A description of what the input should contain   | Yes      |
+
+
+## Examples
+
+### Standard Keyword Microagent Example
+
+Standard keyword microagent file example located at `.openhands/microagents/yummy.md`:
+```yaml
+---
+# The type field is optional and will be inferred as 'knowledge' when triggers are present
 triggers:
 - yummyhappy
 - happyyummy
@@ -33,4 +118,58 @@ triggers:
 The user has said the magic word. Respond with "That was delicious!"
 ```
 
-[See examples of microagents triggered by keywords in the official OpenHands repository](https://github.com/All-Hands-AI/OpenHands/tree/main/microagents)
+### Command-Style Microagent Example
+
+Command-style microagent file example located at `.openhands/microagents/fix_test.md`:
+```yaml
+---
+# The type field is optional and will be inferred as 'task' when inputs are present
+triggers:
+- /fix_test
+inputs:
+  - name: BRANCH_NAME
+    description: "Branch for the agent to work on"
+  - name: TEST_COMMAND_TO_RUN
+    description: "The test command you want the agent to work on. For example, `pytest tests/unit/test_bash_parsing.py`"
+  - name: FUNCTION_TO_FIX
+    description: "The name of function to fix"
+  - name: FILE_FOR_FUNCTION
+    description: "The path of the file that contains the function"
+---
+
+Can you check out branch "{{ BRANCH_NAME }}", and run {{ TEST_COMMAND_TO_RUN }}.
+
+Help me fix these tests to pass by fixing the {{ FUNCTION_TO_FIX }} function in file {{ FILE_FOR_FUNCTION }}.
+
+PLEASE DO NOT modify the tests by yourself -- Let me know if you think some of the tests are incorrect.
+```
+
+## Using Command-Style Microagents
+
+Command-style microagents are designed to streamline common development tasks by providing structured templates for specific operations. They are triggered using a command-style format and will prompt the user for any required inputs.
+
+### How to Use
+
+1. Type `/` in the chat input to see available command-style microagents
+2. Select a microagent from the dropdown or type its name (e.g., `/fix_test`)
+3. The agent will prompt you for any required inputs
+4. Provide the requested information
+5. The agent will execute the task with your inputs
+
+### Template Variables
+
+In the body of a command-style microagent, you can reference input variables using the `{{ VARIABLE_NAME }}` syntax. These will be replaced with the user-provided values when the microagent is triggered.
+
+### Available Command-Style Microagents
+
+OpenHands includes several built-in command-style microagents:
+
+| Command              | Description                                           |
+|----------------------|-------------------------------------------------------|
+| `/fix_test`          | Fix failing tests by modifying a specific function    |
+| `/update_test`       | Update tests for a new implementation                 |
+| `/update_pr`         | Update a pull request description                     |
+| `/address_pr_comments` | Address comments on a pull request                  |
+| `/add_repo_instruction` | Add instructions to the repository microagent      |
+
+[See examples of microagents in the official OpenHands repository](https://github.com/All-Hands-AI/OpenHands/tree/main/microagents)

docs/usage/prompting/microagents-overview.mdx

@@ -8,7 +8,7 @@ description: Microagents are specialized prompts that enhance OpenHands with dom
 Currently OpenHands supports the following types of microagents:
 
 - [General Microagents](./microagents-repo): General guidelines for OpenHands about the repository.
-- [Keyword-Triggered Microagents](./microagents-keyword): Guidelines activated by specific keywords in prompts.
+- [Keyword-Triggered Microagents](./microagents-keyword): Guidelines activated by specific keywords in prompts, including command-style microagents that prompt for user inputs.
 
 To customize OpenHands' behavior, create a .openhands/microagents/ directory in the root of your repository and
 add `<microagent_name>.md` files inside. For repository-specific guidelines, you can ask OpenHands to analyze your repository and create a comprehensive `repo.md` file (see [General Microagents](./microagents-repo) for details).
@@ -34,7 +34,7 @@ some-repository/
 Each microagent file may include frontmatter that provides additional information. In some cases, this frontmatter
 is required:
 
-| Microagent Type                 | Required |
-|---------------------------------|----------|
-| `General Microagents`           | No       |
-| `Keyword-Triggered Microagents` | Yes      |
+| Microagent Type                                | Required |
+|------------------------------------------------|----------|
+| `General Microagents`                          | No       |
+| `Keyword-Triggered Microagents (all types)`    | Yes      |

microagents/add_agent.md

@@ -1,20 +1,17 @@
 ---
-name: add_agent
-type: knowledge
-version: 1.0.0
-agent: CodeActAgent
 triggers:
-  - new agent
-  - new microagent
-  - create agent
-  - create an agent
-  - create microagent
-  - create a microagent
-  - add agent
-  - add an agent
-  - add microagent
-  - add a microagent
-  - microagent template
+- new agent
+- new microagent
+- create agent
+- create an agent
+- create microagent
+- create a microagent
+- add agent
+- add an agent
+- add microagent
+- add a microagent
+- microagent template
+type: knowledge
 ---
 
 This agent helps create new microagents in the `.openhands/microagents` directory by providing guidance and templates.
@@ -38,4 +35,4 @@ For detailed information, see:
 
 - [Microagents Overview](https://docs.all-hands.dev/usage/prompting/microagents-overview)
 - [Microagents Syntax](https://docs.all-hands.dev/usage/prompting/microagents-syntax)
-- [Example GitHub Microagent](https://github.com/All-Hands-AI/OpenHands/blob/main/microagents/github.md)
+- [Example GitHub Microagent](https://github.com/All-Hands-AI/OpenHands/blob/main/microagents/github.md)

microagents/add_repo_inst.md

@@ -1,13 +1,9 @@
 ---
-name: add_repo_inst
-version: 1.0.0
-author: openhands
-agent: CodeActAgent
+inputs:
+- description: Branch for the agent to work on
+  name: REPO_FOLDER_NAME
 triggers:
 - /add_repo_inst
-inputs:
-  - name: REPO_FOLDER_NAME
-    description: "Branch for the agent to work on"
 ---
 
 Please browse the current repository under /workspace/{{ REPO_FOLDER_NAME }}, look at the documentation and relevant code, and understand the purpose of this repository.
@@ -62,4 +58,4 @@ Frontend:
 ```
 
 Now, please write a similar markdown for the current repository.
-Read all the GitHub workflows under .github/ of the repository (if this folder exists) to understand the CI checks (e.g., linter, pre-commit), and include those in the repo.md file.
+Read all the GitHub workflows under .github/ of the repository (if this folder exists) to understand the CI checks (e.g., linter, pre-commit), and include those in the repo.md file.

microagents/address_pr_comments.md

@@ -1,19 +1,15 @@
 ---
-name: address_pr_comments
-version: 1.0.0
-author: openhands
-agent: CodeActAgent
+inputs:
+- description: URL of the pull request
+  name: PR_URL
+- description: Branch name corresponds to the pull request
+  name: BRANCH_NAME
 triggers:
 - /address_pr_comments
-inputs:
-  - name: PR_URL
-    description: "URL of the pull request"
-  - name: BRANCH_NAME
-    description: "Branch name corresponds to the pull request"
 ---
 
 First, check the branch {{ BRANCH_NAME }} and read the diff against the main branch to understand the purpose.
 
 This branch corresponds to this PR {{ PR_URL }}
 
-Next, you should use the GitHub API to read the reviews and comments on this PR and address them.
+Next, you should use the GitHub API to read the reviews and comments on this PR and address them.

microagents/agent_memory.md

@@ -1,10 +1,7 @@
 ---
-name: agent_memory
-type: knowledge
-version: 1.0.0
-agent: CodeActAgent
 triggers:
 - /remember
+type: knowledge
 ---
 
 * Repository memory: Use .openhands/microagents/repo.md under each repository root to store and access important information.
@@ -29,4 +26,4 @@ triggers:
   - If you've only explored a portion of the codebase, clearly note this limitation in the repository structure documentation
   - If you don't know the essential commands for working with the repository, such as lint or typecheck, ask the user and suggest adding them to repo.md for future reference (with permission)
 
-When you receive this message, please review and summarize your recent actions and observations, then present a list of valuable information that should be saved in repo.md to the user.
+When you receive this message, please review and summarize your recent actions and observations, then present a list of valuable information that should be saved in repo.md to the user.

microagents/default-tools.md

@@ -1,15 +1,9 @@
 ---
-# This is a repo microagent that is always activated
-# to include necessary default tools implemented with MCP
-name: default-tools
-type: repo
-version: 1.0.0
-agent: CodeActAgent
 mcp_tools:
   stdio_servers:
-    - name: "fetch"
-      command: "uvx"
-      args: ["mcp-server-fetch"]
-# We leave the body empty because MCP tools will automatically add the
-# tool description for LLMs in tool calls, so there's no need to add extra descriptions.
----
+  - args:
+    - mcp-server-fetch
+    command: uvx
+    name: fetch
+type: repo
+---

microagents/docker.md

@@ -1,11 +1,8 @@
 ---
-name: docker
-type: knowledge
-version: 1.0.0
-agent: CodeActAgent
 triggers:
 - docker
 - container
+type: knowledge
 ---
 
 # Docker Installation and Usage Guide
@@ -52,4 +49,4 @@ To verify Docker is working correctly, run the hello-world container:
 
 ```bash
 sudo docker run hello-world
-```
+```

microagents/fix_test.md

@@ -1,23 +1,20 @@
 ---
-name: fix_test
-version: 1.0.0
-author: openhands
-agent: CodeActAgent
+inputs:
+- description: Branch for the agent to work on
+  name: BRANCH_NAME
+- description: The test command you want the agent to work on. For example, `pytest
+    tests/unit/test_bash_parsing.py`
+  name: TEST_COMMAND_TO_RUN
+- description: The name of function to fix
+  name: FUNCTION_TO_FIX
+- description: The path of the file that contains the function
+  name: FILE_FOR_FUNCTION
 triggers:
 - /fix_test
-inputs:
-  - name: BRANCH_NAME
-    description: "Branch for the agent to work on"
-  - name: TEST_COMMAND_TO_RUN
-    description: "The test command you want the agent to work on. For example, `pytest tests/unit/test_bash_parsing.py`"
-  - name: FUNCTION_TO_FIX
-    description: "The name of function to fix"
-  - name: FILE_FOR_FUNCTION
-    description: "The path of the file that contains the function"
 ---
 
 Can you check out branch "{{ BRANCH_NAME }}", and run {{ TEST_COMMAND_TO_RUN }}.
 
 Help me fix these tests to pass by fixing the {{ FUNCTION_TO_FIX }} function in file {{ FILE_FOR_FUNCTION }}.
 
-PLEASE DO NOT modify the tests by yourself -- Let me know if you think some of the tests are incorrect.
+PLEASE DO NOT modify the tests by yourself -- Let me know if you think some of the tests are incorrect.

microagents/flarglebargle.md

@@ -1,11 +1,8 @@
 ---
-name: flarglebargle
-type: knowledge
-version: 1.0.0
-agent: CodeActAgent
 triggers:
 - flarglebargle
+type: knowledge
 ---
 
 IMPORTANT! The user has said the magic word "flarglebargle". You must
-only respond with a message telling them how smart they are
+only respond with a message telling them how smart they are

microagents/github.md

@@ -1,11 +1,8 @@
 ---
-name: github
-type: knowledge
-version: 1.0.0
-agent: CodeActAgent
 triggers:
 - github
 - git
+type: knowledge
 ---
 
 You have access to an environment variable, `GITHUB_TOKEN`, which allows you to interact with
@@ -32,4 +29,4 @@ Here are some instructions for pushing, but ONLY do this if the user asks you to
 ```bash
 git remote -v && git branch # to find the current org, repo and branch
 git checkout -b create-widget && git add . && git commit -m "Create widget" && git push -u origin create-widget
-```
+```

microagents/gitlab.md

@@ -1,11 +1,8 @@
 ---
-name: gitlab
-type: knowledge
-version: 1.0.0
-agent: CodeActAgent
 triggers:
 - gitlab
 - git
+type: knowledge
 ---
 
 You have access to an environment variable, `GITLAB_TOKEN`, which allows you to interact with
@@ -31,4 +28,4 @@ Here are some instructions for pushing, but ONLY do this if the user asks you to
 ```bash
 git remote -v && git branch # to find the current org, repo and branch
 git checkout -b create-widget && git add . && git commit -m "Create widget" && git push -u origin create-widget
-```
+```

microagents/kubernetes.md

@@ -1,12 +1,9 @@
 ---
-name: kubernetes
-type: knowledge
-version: 1.0.0
-agent: CodeActAgent
 triggers:
 - kubernetes
 - k8s
 - kube
+type: knowledge
 ---
 
 # Kubernetes Local Development with KIND
@@ -47,4 +44,4 @@ Create a basic KIND cluster:
 
 ```bash
 kind create cluster
-```
+```

microagents/npm.md

@@ -1,11 +1,8 @@
 ---
-name: npm
-type: knowledge
-version: 1.0.0
-agent: CodeActAgent
 triggers:
 - npm
+type: knowledge
 ---
 
 When using npm to install packages, you will not be able to use an interactive shell, and it may be hard to confirm your actions.
-As an alternative, you can pipe in the output of the unix "yes" command to confirm your actions.
+As an alternative, you can pipe in the output of the unix "yes" command to confirm your actions.

microagents/pdflatex.md

@@ -1,10 +1,7 @@
 ---
-name: pdflatex
-type: knowledge
-version: 1.0.0
-agent: CodeActAgent
 triggers:
 - pdflatex
+type: knowledge
 ---
 
 PdfLatex is a tool that converts Latex sources into PDF. This is specifically very important for researchers, as they use it to publish their findings. It could be installed very easily using Linux terminal, though this seems an annoying task on Windows. Installation commands are given below.
@@ -33,4 +30,4 @@ Once installed as above, you may be able to create PDF files from latex sources
 pdflatex latex_source_name.tex
 ```
 
-Ref: http://kkpradeeban.blogspot.com/2014/04/installing-latexpdflatex-on-ubuntu.html
+Ref: http://kkpradeeban.blogspot.com/2014/04/installing-latexpdflatex-on-ubuntu.html

microagents/security.md

@@ -1,15 +1,13 @@
 ---
-name: security
-type: knowledge
-version: 1.0.0
-agent: CodeActAgent
 triggers:
-  - security
-  - vulnerability
-  - authentication
-  - authorization
-  - permissions
+- security
+- vulnerability
+- authentication
+- authorization
+- permissions
+type: knowledge
 ---
+
 This document provides guidance on security best practices
 
 You should always be considering security implications when developing.
@@ -31,4 +29,4 @@ You should always complete the task requested. If there are security concerns pl
 - Never expose sensitive information in error messages
 - Log security events appropriately
 - Implement proper exception handling
-- Use secure error reporting mechanisms
+- Use secure error reporting mechanisms

microagents/ssh.md

@@ -1,16 +1,13 @@
 ---
-name: SSH Microagent
-type: knowledge
-version: 1.0.0
-agent: CodeActAgent
 triggers:
-  - ssh
-  - remote server
-  - remote machine
-  - remote host
-  - remote connection
-  - secure shell
-  - ssh keys
+- ssh
+- remote server
+- remote machine
+- remote host
+- remote connection
+- secure shell
+- ssh keys
+type: knowledge
 ---
 
 # SSH Microagent
@@ -134,4 +131,4 @@ chmod 600 ~/.ssh/id_ed25519
 chmod 644 ~/.ssh/id_ed25519.pub
 # Set correct permissions for SSH directory
 chmod 700 ~/.ssh
-```
+```

microagents/swift-linux.md

@@ -1,12 +1,9 @@
 ---
- name: swift-linux
- type: knowledge
- agent: CodeActAgent
- version: 1.0.0
- triggers:
- - swift-linux
- - swift-debian
- - swift-installation
+triggers:
+- swift-linux
+- swift-debian
+- swift-installation
+type: knowledge
 ---
 
 # Swift Installation Guide for Debian Linux
@@ -80,4 +77,4 @@ Verify that Swift is correctly installed by running:
 
 ```bash
 swift --version
-```
+```

microagents/update_pr_description.md

@@ -1,21 +1,17 @@
 ---
-name: update_pr_description
-version: 1.0.0
-author: openhands
-agent: CodeActAgent
+inputs:
+- description: URL of the pull request
+  name: PR_URL
+  type: string
+  validation:
+    pattern: ^https://github.com/.+/.+/pull/[0-9]+$
+- description: Branch name corresponds to the pull request
+  name: BRANCH_NAME
+  type: string
 triggers:
 - /update_pr_description
-inputs:
-  - name: PR_URL
-    description: "URL of the pull request"
-    type: string
-    validation:
-      pattern: "^https://github.com/.+/.+/pull/[0-9]+$"
-  - name: BRANCH_NAME
-    description: "Branch name corresponds to the pull request"
-    type: string
 ---
 
 Please check the branch "{{ BRANCH_NAME }}" and look at the diff against the main branch. This branch belongs to this PR "{{ PR_URL }}".
 
-Once you understand the purpose of the diff, please use Github API to read the existing PR description, and update it to be more reflective of the changes we've made when necessary.
+Once you understand the purpose of the diff, please use Github API to read the existing PR description, and update it to be more reflective of the changes we've made when necessary.

microagents/update_test.md

@@ -1,19 +1,16 @@
 ---
-name: update_test
-version: 1.0.0
-author: openhands
-agent: CodeActAgent
+inputs:
+- description: Branch for the agent to work on
+  name: BRANCH_NAME
+- description: The test command you want the agent to work on. For example, `pytest
+    tests/unit/test_bash_parsing.py`
+  name: TEST_COMMAND_TO_RUN
 triggers:
 - /update_test
-inputs:
-  - name: BRANCH_NAME
-    description: "Branch for the agent to work on"
-  - name: TEST_COMMAND_TO_RUN
-    description: "The test command you want the agent to work on. For example, `pytest tests/unit/test_bash_parsing.py`"
 ---
 
 Can you check out branch "{{ BRANCH_NAME }}", and run {{ TEST_COMMAND_TO_RUN }}.
 
 The current implementation of the code is correct BUT the test functions {{ FUNCTION_TO_FIX }} in file {{ FILE_FOR_FUNCTION }} are failing.
 
-Please update the test file so that they pass with the current version of the implementation.
+Please update the test file so that they pass with the current version of the implementation.

openhands/microagent/microagent.py

@@ -103,7 +103,9 @@ class BaseMicroagent(BaseModel):
         if metadata.inputs:
             inferred_type = MicroagentType.TASK
             # Add a trigger for the agent name if not already present
-            trigger = f'/{metadata.name}'
+            # Use derived_name if available, otherwise use metadata.name
+            agent_name = derived_name if derived_name is not None and (metadata.name == 'default' or not metadata.name) else metadata.name
+            trigger = f'/{agent_name}'
             if not metadata.triggers or trigger not in metadata.triggers:
                 if not metadata.triggers:
                     metadata.triggers = [trigger]
@@ -121,7 +123,11 @@ class BaseMicroagent(BaseModel):
             raise ValueError(f'Could not determine microagent type for: {path}')
 
         # Use derived_name if available (from relative path), otherwise fallback to metadata.name
-        agent_name = derived_name if derived_name is not None else metadata.name
+        # If metadata.name is still the default 'default', use the derived_name
+        if derived_name is not None and (metadata.name == 'default' or not metadata.name):
+            agent_name = derived_name
+        else:
+            agent_name = metadata.name
 
         agent_class = subclass_map[inferred_type]
         return agent_class(

openhands/microagent/types.py

@@ -27,8 +27,10 @@ class MicroagentMetadata(BaseModel):
 
     name: str = 'default'
     type: MicroagentType = Field(default=MicroagentType.REPO_KNOWLEDGE)
-    version: str = Field(default='1.0.0')
-    agent: str = Field(default='CodeActAgent')
+    # Keep these fields for backward compatibility but they're not used
+    version: str = Field(default='1.0.0', exclude=True)
+    agent: str = Field(default='CodeActAgent', exclude=True)
+    author: str = Field(default='', exclude=True)
     triggers: list[str] = []  # optional, only exists for knowledge microagents
     inputs: list[InputMetadata] = []  # optional, only exists for task microagents
     mcp_tools: MCPConfig | None = (

tests/runtime/test_microagent.py

@@ -373,9 +373,9 @@ def test_default_tools_microagent_exists():
     assert 'type: repo' in content, 'default-tools.md should be a repo microagent'
 
     # Verify it has the fetch tool configured
-    assert 'name: "fetch"' in content, 'default-tools.md should have a fetch tool'
-    assert 'command: "uvx"' in content, 'default-tools.md should use uvx command'
-    assert 'args: ["mcp-server-fetch"]' in content, (
+    assert 'name: "fetch"' in content or 'name: fetch' in content, 'default-tools.md should have a fetch tool'
+    assert 'command: uvx' in content, 'default-tools.md should use uvx command'
+    assert 'mcp-server-fetch' in content, (
         'default-tools.md should use mcp-server-fetch'
     )