Website Generator
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| b12_website_generatorC | |
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 possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as generating a website based on business name and description, making it distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The tool name 'b12_website_generator' follows a clear noun-based pattern without any conflicting conventions.
A single tool for a 'Website Generator' server is too minimal for the apparent scope. This domain typically requires multiple operations like editing, publishing, or managing templates, making one tool feel incomplete and limiting for agent workflows.
The tool set is severely incomplete for website generation. It only covers initial creation, with no tools for updates, deletions, content management, or other lifecycle operations, leaving significant gaps that will hinder agent functionality.