Skip to content

docs(mcp): troubleshooting row covers the MCP enum validation error #34

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ghchinoy merged 1 commit into from
Sep 29, 2026
Merged

docs(mcp): troubleshooting row covers the MCP enum validation error #34

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs-site/src/content/docs/reference/studio-mcp-api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -235,7 +235,7 @@ response.
| `max_entropy` or `gpu_forward_ms` is always `0` | The binary or hosted gateway predates issue #14. Rebuild or redeploy. |
| Calls fail with `HTTP 429` or take minutes | A Cloud Run or Vertex backend is waking from zero. Call `get_health_and_gpu_status`, and `warmup_gpu` with `wait_for_ready: false` before a batch. |
| Plain `dgem mcp` calls go to `127.0.0.1:8080` | No endpoints were configured; see Option B, or use `--remote` (Option A). |
| `backend "vertex" is not enabled on this gateway (available: local)` | The `backend` argument names a backend that isn't configured. It's no longer rerouted silently. Omit `backend` to use the default, pick one from the list, or configure it: `DGEM_VERTEX_URL` / `--vertex-url` for `vertex` and `vertex_first`, `-u` for `cloudrun`. On a hosted gateway the operator may also restrict backends with `DGEM_BACKENDS`. |
| `validating /properties/backend: enum: vertex does not equal any of: [local]` (MCP), or `backend "vertex" is not enabled on this gateway (available: local)` (HTTP API, and MCP `locate_bounding_boxes` on a local-only server) | The `backend` argument names a backend that isn't configured. It's no longer rerouted silently. Each MCP tool's schema lists the configured backends as an `enum`, so the MCP server rejects any other value before the call runs; the list in brackets is what this server offers. Omit `backend` to use the default, pick one from the list, or configure it: `DGEM_VERTEX_URL` / `--vertex-url` for `vertex` and `vertex_first`, `-u` for `cloudrun`. On a hosted gateway the operator may also restrict backends with `DGEM_BACKENDS`. |
| `vertex_url "..." is not allowed on this gateway` | `vertex_url` may only name the configured endpoint, or one listed in `--allowed-vertex-endpoints` (`DGEM_ALLOWED_VERTEX_ENDPOINTS`) on `dgem serve`. Drop the argument to use the configured endpoint. |

To check what a `dgem` binary advertises without an agent, pipe `initialize` and `tools/list` into it (the
Expand Down
2 changes: 1 addition & 1 deletion docs/reference/studio-mcp-api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -237,7 +237,7 @@ response.
| `max_entropy` or `gpu_forward_ms` is always `0` | The binary or hosted gateway predates issue #14. Rebuild or redeploy. |
| Calls fail with `HTTP 429` or take minutes | A Cloud Run or Vertex backend is waking from zero. Call `get_health_and_gpu_status`, and `warmup_gpu` with `wait_for_ready: false` before a batch. |
| Plain `dgem mcp` calls go to `127.0.0.1:8080` | No endpoints were configured; see Option B, or use `--remote` (Option A). |
| `backend "vertex" is not enabled on this gateway (available: local)` | The `backend` argument names a backend that isn't configured. It's no longer rerouted silently. Omit `backend` to use the default, pick one from the list, or configure it: `DGEM_VERTEX_URL` / `--vertex-url` for `vertex` and `vertex_first`, `-u` for `cloudrun`. On a hosted gateway the operator may also restrict backends with `DGEM_BACKENDS`. |
| `validating /properties/backend: enum: vertex does not equal any of: [local]` (MCP), or `backend "vertex" is not enabled on this gateway (available: local)` (HTTP API, and MCP `locate_bounding_boxes` on a local-only server) | The `backend` argument names a backend that isn't configured. It's no longer rerouted silently. Each MCP tool's schema lists the configured backends as an `enum`, so the MCP server rejects any other value before the call runs; the list in brackets is what this server offers. Omit `backend` to use the default, pick one from the list, or configure it: `DGEM_VERTEX_URL` / `--vertex-url` for `vertex` and `vertex_first`, `-u` for `cloudrun`. On a hosted gateway the operator may also restrict backends with `DGEM_BACKENDS`. |
| `vertex_url "..." is not allowed on this gateway` | `vertex_url` may only name the configured endpoint, or one listed in `--allowed-vertex-endpoints` (`DGEM_ALLOWED_VERTEX_ENDPOINTS`) on `dgem serve`. Drop the argument to use the configured endpoint. |

To check what a `dgem` binary advertises without an agent, pipe `initialize` and `tools/list` into it (the
Expand Down
Loading