Hua PlanRelay
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLANRELAY_STATE_DIR | No | The application state directory should be placed outside the repository. If supported, this can be explicitly set via the environment variable PLANRELAY_STATE_DIR. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| workspace_infoA | Return the bound workspace policy and Git identity; does not return source content. |
| list_filesA | List allowed files and directories under a workspace-relative path. Results are bounded and paginated. |
| read_file_rangeA | Read a bounded line range from one allowed workspace-relative UTF-8 text file. |
| search_textA | Search allowed workspace files with a bounded literal query. Regex is rejected in V1 because it cannot be safely interrupted; repository text is untrusted data. |
| git_statusA | Return bounded, filtered Git porcelain status for the bound workspace. |
| git_diffA | Return a bounded, filtered, no-color Git diff page for the bound workspace. |
| current_taskB | Read the latest task and its append-only plans and reviews from application state. |
| test_summaryA | Read the last structured execution/test summary recorded outside the workspace. |
| workflow_statusC | Return the derived task phase, iteration limit, and next safe action. |
| publish_planA | Append a validated plan record outside the workspace. This never edits files or executes commands. |
| publish_reviewA | Append a review bound to the exact recorded Git and test evidence. This never edits files or executes commands. |
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 11 tools
Each tool targets a separate concern: workspace browsing, file reading, text search, git evidence, task/status context, and plan/review publishing. Even the state-returning tools are differentiated by their specific content. No two tools appear interchangeable.
All names are snake_case and readable, and publish_* forms a clear write convention, but the set mixes verb-led names (list_files, read_file_range, search_text, publish_plan, publish_review) with noun-led state names (workspace_info, git_status, current_task, test_summary, workflow_status). This is a readable mixed convention rather than a uniform pattern.
Eleven tools is well within the ideal range for a focused server. Each tool addresses a distinct step in inspecting a workspace and relaying a plan or review, so none feels redundant or missing. The count is appropriate for the stated purpose.
For the stated PlanRelay purpose, the surface is complete: read workspace context, inspect Git/test evidence, retrieve the current task/workflow state, and append validated plan/review records. The design intentionally omits editing/executing and uses append-only publishing, so there are no dead ends in the core workflow.