Document Generator MCP
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 |
|---|---|
| gerar_documento_wordC | Cria um arquivo Microsoft Word (.docx) |
| gerar_documento_pdfC | Cria um arquivo PDF |
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 perfectly distinct purposes: one creates PDF files and the other creates Word documents. There is no overlap in functionality or ambiguity about which tool to use for each file type.
Both tools follow an identical naming pattern: 'gerar_documento_' followed by the file format. This consistent verb_noun structure in Portuguese makes the tool names predictable and easy to understand.
With only two tools, the server feels thin for a 'Document Generator' domain. While it covers two common formats, there are obvious gaps for other document types (e.g., HTML, plain text) and operations like editing or converting existing documents.
The tool surface is severely incomplete for document generation. It lacks support for multiple document formats beyond PDF and Word, and provides no operations for document manipulation, conversion, or template management that would be expected in this domain.