io.github.xfloukiex-lab/road-poneglyph
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_poneglyphA | Reveal the 'Void History' of a plan. Uncovers hidden risks, missing technical dependencies, and completely unstated assumptions. Pass the plan/code/architecture you want decoded. Args: current_plan: The proposal, code snippet, feature set, or architecture. project_type: Category (e.g. SaaS, Mobile App, AI Agent, Protocol Design). |
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
With only one tool, there is no risk of confusion between tools. The single tool's purpose is clearly described.
The single tool name 'read_poneglyph' follows a clear verb_noun pattern, which is consistent and descriptive.
A single tool for broad plan analysis feels thin for the scope implied. While functional, it could be expanded into multiple specialized tools.
The tool claims to uncover risks, dependencies, and assumptions, bundling multiple analyses into one. This covers the basic need but lacks granularity for complex scenarios.