Fix param style consistency

Author: danbarr

docs/toolhive/guides-cli/api-server.md

@@ -45,14 +45,14 @@ By default, the API server listens on `localhost` (127.0.0.1) port `8080`.
 You can specify a different port using the `--port` option:
 
 ```bash
-thv serve --port <port-number>
+thv serve --port <PORT_NUMBER>
 ```
 
 If you're running the API server on a remote host, specify the hostname or IP
 address to bind to using the `--host` option:
 
 ```bash
-thv serve --host <host-name>
+thv serve --host <HOSTNAME_OR_IP>
 ```
 
 ## UNIX socket support

docs/toolhive/guides-cli/install.mdx

@@ -166,7 +166,7 @@ otherwise the upgrade will fail because Windows locks the executable while it
 runs.
 
 Run `thv stop --all` to stop all running servers. After you complete the
-upgrade, restart them using `thv restart <server-name>`.
+upgrade, restart them using `thv restart <SERVER_NAME>`.
 
 :::
 
@@ -214,7 +214,7 @@ ToolHive has built-in help for all commands:
 thv --help
 
 # Help for a specific command
-thv <command> --help
+thv <COMMAND> --help
 ```
 
 For detailed documentation on each command, see the
@@ -252,7 +252,7 @@ To uninstall ToolHive:
    thv list
    # Stop and remove each server
    thv stop --all
-   thv rm <server-name>
+   thv rm <SERVER_NAME>
    ```
 
 2. Remove all ToolHive configuration and log files:
@@ -389,7 +389,7 @@ To resolve this:
 
    ```powershell
    thv list --all
-   thv restart <server-name>
+   thv restart <SERVER_NAME>
    # repeat for each server
    ```
 

docs/toolhive/guides-cli/manage-mcp-servers.md

@@ -33,14 +33,14 @@ the logs with the `--follow` option, which shows the most recent log entries and
 updates in real time.
 
 ```bash
-thv logs <server-name> [--follow]
+thv logs <SERVER_NAME> [--follow]
 ```
 
 Logs are stored in the ToolHive application directory. The path depends on your
 platform:
 
-- **macOS**: `~/Library/Application Support/toolhive/logs/<server-name>.log`
-- **Linux**: `~/.local/share/toolhive/logs/<server-name>.log`
+- **macOS**: `~/Library/Application Support/toolhive/logs/<SERVER_NAME>.log`
+- **Linux**: `~/.local/share/toolhive/logs/<SERVER_NAME>.log`
 
 The specific log file path is displayed when you start a server with
 [`thv run`](../reference/cli/thv_run.md).
@@ -56,7 +56,7 @@ with the ToolHive CLI and MCP servers.
 To stop a running MCP server:
 
 ```bash
-thv stop <server-name>
+thv stop <SERVER_NAME>
 ```
 
 This stops the server and the associated proxy process, removes the MCP server's
@@ -69,15 +69,15 @@ Add the `--all` flag to stop all running servers.
 To restart a stopped MCP server and add it back to your configured clients:
 
 ```bash
-thv restart <server-name>
+thv restart <SERVER_NAME>
 ```
 
 ### Remove a server
 
 To remove an MCP server:
 
 ```bash
-thv rm <server-name>
+thv rm <SERVER_NAME>
 ```
 
 This removes the container and cleans up the MCP server's entry in your

docs/toolhive/guides-cli/registry.md

@@ -41,7 +41,7 @@ You can also search by keyword to find servers related to a specific topic or
 capability:
 
 ```bash
-thv search <term>
+thv search <TERM>
 ```
 
 For example, to locate servers related to GitHub:
@@ -55,7 +55,7 @@ thv search github
 To view detailed information about a specific MCP server, run:
 
 ```bash
-thv registry info <server-name>
+thv registry info <SERVER_NAME>
 ```
 
 For example:
@@ -71,7 +71,7 @@ By default, ToolHive displays the server's configuration in a human-readable
 format. To view the configuration in JSON format, use the `--format` option:
 
 ```bash
-thv registry info <server-name> --format json
+thv registry info <SERVER_NAME> --format json
 ```
 
 ### Example output
@@ -135,7 +135,7 @@ organizations that want to maintain their own private registry of MCP servers.
 To configure ToolHive to use a remote registry, set the registry URL:
 
 ```bash
-thv config set-registry-url <url>
+thv config set-registry-url <URL>
 ```
 
 For example:

docs/toolhive/guides-cli/secrets-management.mdx

@@ -102,7 +102,7 @@ create or update a secret in your secret store. You can set a secret
 interactively by running:
 
 ```bash
-thv secret set <secret-name>
+thv secret set <SECRET_NAME>
 ```
 
 ToolHive prompts you to enter the secret value, and the input remains hidden for
@@ -118,7 +118,7 @@ thv secret set github
 Alternatively, you can set a secret using standard input:
 
 ```bash
-echo "MY_SECRET_VALUE" | thv secret set <secret-name>
+echo "MY_SECRET_VALUE" | thv secret set <SECRET_NAME>
 ```
 
 :::tip Example
@@ -144,15 +144,15 @@ thv secret list
 To decrypt and view a secret's value:
 
 ```bash
-thv secret get <secret-name>
+thv secret get <SECRET_NAME>
 ```
 
 ### Remove a secret
 
 To delete a secret when it's no longer needed:
 
 ```bash
-thv secret delete <secret-name>
+thv secret delete <SECRET_NAME>
 ```
 
 ### Reset your secret store
@@ -206,7 +206,7 @@ To do this, use the `--secret` flag with the
 into the container as an environment variable.
 
 ```bash
-thv run --secret <secret-name>,target=<ENV_VAR_NAME> <server-name>
+thv run --secret <SECRET_NAME>,target=<ENV_VAR_NAME> <SERVER>
 ```
 
 Check the MCP server's documentation to find the expected environment variable
@@ -217,7 +217,7 @@ For MCP servers in the ToolHive registry, you can find the expected environment
 variable names in the server's registry entry:
 
 ```bash
-thv registry info <server-name>
+thv registry info <SERVER_NAME>
 ```
 
 ### Example: GitHub API token
@@ -310,21 +310,21 @@ If your MCP server can't access a secret:
 2. Verify the secret value:
 
    ```bash
-   thv secret get <secret-name>
+   thv secret get <SECRET_NAME>
    ```
 
 3. Check that you're using the correct secret name and target environment
    variable. Inspect the MCP server's expected environment variables in the
    registry:
 
    ```bash
-   thv registry info <server-name>
+   thv registry info <SERVER_NAME>
    ```
 
 4. Inspect the server logs for any errors:
 
    ```bash
-   thv logs <server-name>
+   thv logs <SERVER_NAME>
    ```
 
 </details>

docs/toolhive/guides-k8s/deploy-operator-helm.md

@@ -29,7 +29,7 @@ helm upgrade -i toolhive-operator-crds oci://ghcr.io/stacklok/toolhive/toolhive-
 ```
 
 This command installs the latest version of the ToolHive operator CRDs Helm
-chart. To install a specific version, append `--version <version>` to the
+chart. To install a specific version, append `--version <VERSION>` to the
 command, for example:
 
 ```bash
@@ -48,7 +48,7 @@ helm upgrade -i toolhive-operator oci://ghcr.io/stacklok/toolhive/toolhive-opera
 ```
 
 This command installs the latest version of the ToolHive operator CRDs Helm
-chart. To install a specific version, append `--version <version>` to the
+chart. To install a specific version, append `--version <VERSION>` to the
 command, for example:
 
 ```bash
@@ -66,7 +66,7 @@ After about 30 seconds, you should see the `toolhive-operator` pod running.
 Check the logs of the operator pod:
 
 ```bash
-kubectl logs -f -n toolhive-system <toolhive-operator-pod-name>
+kubectl logs -f -n toolhive-system <TOOLHIVE_OPERATOR_POD_NAME>
 ```
 
 This shows you the logs of the operator pod, which can help you debug any
@@ -217,7 +217,7 @@ kubectl get clusterrolebinding | grep toolhive
 # Check operator pod status
 kubectl get pods -n toolhive-system
 # Check operator pod logs
-kubectl logs -n toolhive-system <toolhive-operator-pod-name>
+kubectl logs -n toolhive-system <TOOLHIVE_OPERATOR_POD_NAME>
 ```
 
 ## Upgrade the operator
@@ -291,8 +291,8 @@ the pod logs for error messages:
 kubectl get pods -n toolhive-system
 # Note the name of the toolhive-operator pod
 
-kubectl describe pod -n toolhive-system <toolhive-operator-pod-name>
-kubectl logs -n toolhive-system <toolhive-operator-pod-name>
+kubectl describe pod -n toolhive-system <TOOLHIVE_OPERATOR_POD_NAME>
+kubectl logs -n toolhive-system <TOOLHIVE_OPERATOR_POD_NAME>
 ```
 
 Common causes include:
@@ -320,7 +320,7 @@ permission issues:
 kubectl get crd | grep toolhive
 
 # Remove existing CRDs if needed (this will delete all related resources)
-kubectl delete crd <crd-name>
+kubectl delete crd <CRD_NAME>
 ```
 
 To reinstall the CRDs:

docs/toolhive/tutorials/quickstart-cli.mdx

@@ -288,7 +288,7 @@ server. Here are some next steps to explore:
 
 - Try running other MCP servers from the registry with
   [`thv registry list`](../reference/cli/thv_registry_list.md) and
-  [`thv run <server-name>`](../reference/cli/thv_run.md)
+  [`thv run`](../reference/cli/thv_run.md)
 - Learn about [secrets management](../guides-cli/secrets-management.mdx) for MCP
   servers that require authentication
 - Explore [custom permissions](../guides-cli/custom-permissions.mdx) for MCP