Glyphic
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_schemaA | Returns the JSON schema of the DiagramInput payload to help the AI understand supported diagram types and properties. |
| render_diagramB | Renders a declarative JSON diagram into a visual representation. The input MUST conform to the DiagramInput schema. |
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 2 tools
The two tools have completely distinct purposes: one returns the JSON schema, the other renders a diagram. There is no overlap or ambiguity.
Both tool names follow the verb_noun pattern (get_schema, render_diagram), providing clear and consistent naming.
With only 2 tools, the server feels minimal but appropriate for a focused rendering service. It is slightly under what is typical, but not unreasonable.
The pair covers the core workflow: obtain the schema and then render a diagram. Missing validation or diagram management tools are minor gaps given the narrow scope.