Skip to main content
Glama
backsoul

Dynamic Form MCP

by backsoul

get-answers

Retrieve form responses using a form's unique identifier. This tool fetches submitted answers from dynamic forms for analysis or processing.

Instructions

Obtiene las respuestas de un formulario existente mediante su UUID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesUUID del formulario

Implementation Reference

  • src/index.ts:76-88 (registration)
    Full registration of the 'get-answers' tool using server.tool(), including the tool name, description, input schema (UUID), and the complete handler function that fetches and returns form answers.
    server.tool(
      "get-answers",
      "Obtiene las respuestas de un formulario existente mediante su UUID",
      { uuid: z.string().uuid().describe("UUID del formulario") },
      async ({ uuid }) => {
        const form = new DynamicForm(uuid);
        const { answers, error } = await form.getAnswers();
        if (error) {
          return { content: [{ type: "text", text: `Error al obtener las respuestas: ${error}` }] };
        }
        return { content: [{ type: "text", text: JSON.stringify(answers) }] };
      }
    );
  • The handler function implementing the core logic of the 'get-answers' tool: instantiates DynamicForm with UUID, calls getAnswers(), handles errors, and formats the response as MCP content.
    async ({ uuid }) => {
      const form = new DynamicForm(uuid);
      const { answers, error } = await form.getAnswers();
      if (error) {
        return { content: [{ type: "text", text: `Error al obtener las respuestas: ${error}` }] };
      }
      return { content: [{ type: "text", text: JSON.stringify(answers) }] };
    }
  • Zod input schema for the 'get-answers' tool, validating a single 'uuid' parameter as a string UUID.
    { uuid: z.string().uuid().describe("UUID del formulario") },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it retrieves answers from an existing form via UUID, implying a read-only operation, but doesn't clarify permissions needed, error handling (e.g., invalid UUID), rate limits, or what the return format looks like (e.g., structured data). For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, with every part contributing to understanding the action and resource. There is zero waste, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on usage guidelines, behavioral traits, and output expectations. Without annotations or an output schema, the description should do more to compensate, but it meets a bare minimum for a simple read operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, with the single parameter 'uuid' fully documented in the schema as 'UUID del formulario'. The description adds no additional meaning beyond this, as it only references the UUID without explaining its format or source. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but doesn't need to given the schema's completeness.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('obtiene las respuestas' - gets answers) and the resource ('de un formulario existente' - from an existing form), using a specific verb and target. It distinguishes from siblings like 'get-form' by specifying it retrieves answers rather than the form itself. However, it doesn't explicitly differentiate from 'create-answers' beyond the verb difference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid UUID), exclusions, or comparisons to sibling tools like 'get-form' (which might retrieve form structure) or 'create-answers' (which creates answers). Usage is implied through the verb 'obtiene' but not explicitly defined.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/backsoul/dynamicform-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server