writulos-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WRITULOS_API_KEY | Yes | Your Writulos Scribe API key, e.g. writ_YOUR_API_KEY. Required for tool calls; without it the server starts but tool calls return where to get a key. | |
| WRITULOS_OUTPUT_DIR | No | Directory to write the run log to. By default the server writes docs/writulos.log. |
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 |
|---|---|
| generate_docsA | Generate markdown documentation for a single code file using Writulos. Uses one generation from the account's monthly allowance. |
| generate_docs_batchA | Generate markdown documentation for multiple code files in one request (up to 20 files). Uses one generation per file from the account's monthly allowance. |
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 clearly distinct purposes: generate_docs handles a single file while generate_docs_batch handles multiple files (up to 20). The boundary between them is unambiguous, so an agent can select correctly.
Both names follow a consistent snake_case verb_noun pattern (generate_docs), with the batch variant distinguished by a clean suffix. No mixed conventions or stylistic drift.
Two tools is on the thin side for the stated domain. While each tool earns its place, the surface feels minimal and could likely support additional operations like allowance checks or retrieval.
The server covers the core documentation-generation action, but there are notable gaps: no way to check remaining monthly allowance, list previously generated docs, or retrieve/read generated output. Agents will hit dead ends for anything beyond fire-and-forget generation.