argon-bridge-9router
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEADLESS | No | Whether to run the Playwright Chromium browser in headless mode. | true |
| JIO_COMBO_NAME | No | The name of the 9Router Smart Combo to use for fallback. | jio-max-non-gemini |
| FALLBACK_MODELS | No | Comma-separated list of fallback model IDs or 9Router Smart Combo names. | jio-max-non-gemini,ag/claude-opus-4-6-thinking,ag/claude-sonnet-4-6-thinking,qoder/qwen3-coder-plus,ag/gpt-oss-120b-medium |
| NINE_ROUTER_KEY | Yes | Your 9Router API key. | |
| NINE_ROUTER_URL | No | The base URL of the 9Router OpenAI-compatible endpoint. | http://localhost:20128/v1 |
| PLAYWRIGHT_BRIDGE_PORT | No | The local port used by the OpenAI-compatible Playwright bridge. | 20129 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_argon_playwright_9routerB | Execute coding, architecture, or debugging prompts via Gemini 4 Argon (Playwright Web Bridge) or any 9Router provider/model (including Qoder, Antigravity Claude Opus/Sonnet 4.6, Qwen, DeepSeek, or custom Smart Combos). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool on the server, so there is nothing for an agent to confuse it with. Its purpose (proxying a prompt to a chosen provider/model) is stated explicitly.
The single name uses snake_case and a clear verb ('ask_'), but it redundantly bakes in the server/bridge name and a provider ('argon_playwright_9router'), making it long and vendor-specific. With only one tool there is no cross-tool pattern to break.
A router spanning many providers/models plus a Playwright web bridge is a lot of surface compressed into one opaque passthrough tool. There is no way to discover providers/models or check bridge health without invoking the single call.
The core 'send a prompt' operation exists, but the obvious lifecycle around it is missing: listing available providers/models/combos, checking bridge or session status, and any error/retry or cancellation path. Agents are left with a single fire-and-hope entry point.