Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
render_diagramA

Render an ASCII/Unicode box diagram as SVG (or a web page), keeping every character in its exact cell. Writes output_path and returns a JSON report: read 'status' (ok | warnings | self_check_failed | bad_input) and 'summary'. For warnings, apply each 'hint' (it names the row/col to fix) and render again. Pick 'preset' from where the diagram is going. Run check_diagram first on a new diagram.

check_diagramA

Validate an ASCII/Unicode box diagram without writing anything. Returns 'status', 'summary', warnings with concrete 'hint's (e.g. 'the arrowhead v at row 5 col 5 is one column right'), and the structure: boxes and edges (which box each arrow connects). Use it to confirm a diagram means what you intended before rendering.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 2 tools

Disambiguation5/5

Each tool has a single, distinct role in the pipeline: check_diagram validates and reports diagnostics, while render_diagram writes the output file. There is no overlap or ambiguity about which tool to call for a given step.

Naming Consistency5/5

Both tool names follow the same verb_noun snake_case pattern: check_diagram and render_diagram. The action-object relationship is immediately clear and consistent.

Tool Count4/5

Two tools is slightly below the typical 3-15 range, but for this narrow ASCII-to-SVG purpose the count is reasonable and each tool is essential to the workflow. It feels minimal rather than padded.

Completeness5/5

The validate-then-render lifecycle is fully covered: check_diagram provides structural feedback and hints, and render_diagram produces the output with a status report. There are no obvious missing operations for the stated domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues