Dynamic Form 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create-formC | Crea un formulario dinámico con campos personalizados |
| get-formC | Obtiene la estructura de un formulario existente mediante su UUID |
| get-answersB | Obtiene las respuestas de un formulario existente mediante su UUID |
| create-answersC | Agrega múltiples respuestas a uno o varios formularios mediante sus UUID y los índices de campo |
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 4 tools
Each tool has a clearly distinct purpose: create-form and get-form handle form structure, while create-answers and get-answers handle form responses. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the desired action (create vs. get) and target (form vs. answers).
All tool names follow a consistent verb-noun pattern with hyphens (e.g., create-answers, get-form). The verbs 'create' and 'get' are used predictably across the set, and the nouns 'form' and 'answers' clearly indicate the resource type, ensuring readability and predictability.
With 4 tools, this server is well-scoped for managing dynamic forms, covering both form creation/retrieval and answer submission/retrieval. Each tool earns its place by addressing a core aspect of the domain without being overly sparse or bloated.
The tool set provides complete CRUD coverage for forms (create and get) and answers (create and get), with no dead ends for basic workflows. A minor gap exists in missing update or delete operations for forms and answers, which agents might need to work around, but core functionality is well-covered.