flow-router
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| config | Yes | Path to the flows configuration JSON file containing your routes/triggers (scaffold one with `flow-router init my-flows.json`). Passed as the `--config` argument to the MCP server, e.g. `flow-router --config /path/to/flows.json serve-mcp`. |
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 |
|---|---|
| routeA | 把一句中文用户请求路由到预定义流程之一；无法确定时明确拒答（abstained=true），不要猜。 |
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, so there is no possibility of selecting the wrong one. Its purpose—routing a Chinese request to a predefined flow, or abstaining—is unambiguous within itself.
The single tool 'route' is a clean, lowercase verb that accurately describes its action. With one name there is no convention mixing to penalize.
A router naturally collapses to one decision point, so the minimal surface is defensible rather than accidental. It is still thin overall—there are no supporting tools for inspecting the flow catalog the router chooses from.
The core decision operation exists, but there is no tool to list or describe the available predefined flows, so an agent cannot learn the valid targets or verify a returned flow id. This is a notable discoverability gap for a routing domain.