Skip to main content
Glama
agilesix

VA Form Generation MCP Server

by agilesix

validate_form

Validate VA forms for schema compliance, syntax errors, and apostrophe usage to ensure adherence to VA.gov content standards and best practices.

Instructions

Run validation checks on a form (schema, syntax, apostrophes)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
form_pathYesPath to form directory
check_typesYesTypes of checks to run

Implementation Reference

  • The handler for the 'validate_form' tool, which runs various validation checks (schema, apostrophes, imports, syntax) based on user input.
    case 'validate_form': {
      const { form_path, check_types } = args;
      const checks = check_types.includes('all')
        ? ['schema', 'syntax', 'apostrophes', 'imports']
        : check_types;
    
      const results = [];
    
      for (const checkType of checks) {
        switch (checkType) {
          case 'schema':
            results.push('## Schema Validation\n\nCommand to find uncalled radioSchema:\n```bash\ngrep -rn ": radioSchema[,\\s]" ' + form_path + '/pages/\n```');
            break;
          case 'apostrophes':
            results.push('## Apostrophe Syntax Check\n\nCommand to find strings with apostrophes:\n```bash\ngrep -rn "\'\\w.*\'\\w.*\'" ' + form_path + '/ --include="*.js" --include="*.jsx"\n```');
            break;
          case 'imports':
            results.push('## Import Path Check\n\nCommand to find old import paths:\n```bash\ngrep -rn "web-component-patterns/" ' + form_path + '/\n```');
            break;
          case 'syntax':
            results.push('## Syntax Validation\n\nCommand to run linter:\n```bash\nnpm run lint -- ' + form_path + '/\n```');
            break;
        }
      }
    
      return {
        content: [
          {
            type: 'text',
            text: '# Validation Report\n\n' + results.join('\n\n'),
          },
        ],
      };
    }
  • index.js:98-118 (registration)
    The tool registration for 'validate_form' in the ListToolsRequestSchema handler.
      name: 'validate_form',
      description: 'Run validation checks on a form (schema, syntax, apostrophes)',
      inputSchema: {
        type: 'object',
        properties: {
          form_path: {
            type: 'string',
            description: 'Path to form directory',
          },
          check_types: {
            type: 'array',
            items: {
              type: 'string',
              enum: ['schema', 'syntax', 'apostrophes', 'imports', 'all'],
            },
            description: 'Types of checks to run',
          },
        },
        required: ['form_path', 'check_types'],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the types of checks but doesn't cover critical aspects like whether this is a read-only operation, potential side effects, error handling, or performance implications. This leaves significant gaps for a validation tool.

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 with no wasted words. It front-loads the core action and lists key check types, making it easy to scan and understand quickly.

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 moderate complexity (validation with multiple check types), no annotations, and no output schema, the description is minimally adequate. It covers the basic purpose but lacks details on behavior, results, or integration with siblings, leaving room for improvement in completeness.

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?

Schema description coverage is 100%, so the schema fully documents both parameters. The description lists check types (schema, syntax, apostrophes), which partially aligns with the 'check_types' enum but omits 'imports' and 'all'. It adds minimal value beyond the schema, meeting the baseline for high coverage.

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 tool's purpose with a specific verb ('Run validation checks') and resource ('on a form'), and lists the types of checks (schema, syntax, apostrophes). It distinguishes the tool's function well, though it doesn't explicitly differentiate from sibling tools like 'audit_form'.

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 like 'audit_form' or other siblings. It lacks context on prerequisites, typical use cases, or exclusions, leaving the agent with no usage direction beyond the basic function.

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/agilesix/va-form-generation-mcp'

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