Skip to main content
Glama
agilesix

VA Form Generation MCP Server

by agilesix

get_fix_reference

Retrieve reference guides for fixing common VA form issues like yes/no UI, radio schemas, apostrophes, transformers, and full name paths to ensure compliance with VA.gov standards.

Instructions

Get quick reference for common fixes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fix_typeYesType of fix to get reference for

Implementation Reference

  • The 'get_fix_reference' tool implementation within the CallToolRequestSchema handler. It takes a 'fix_type' and returns the corresponding fix example from a dictionary.
        case 'get_fix_reference': {
          const { fix_type } = args;
    
          const fixes = {
            yesNoUI: `## Fix: yesNoUI Pattern
    
    **Problem:** Complex object form with labelHeaderLevel, custom labels, errorMessages
    
    **Solution:** Simple pattern
    
    \`\`\`javascript
    // BEFORE (WRONG):
    yesNoUI({
      title: 'Are you a patient in a nursing home?',
      labelHeaderLevel: '3',
      labels: { Y: 'Yes', N: 'No' },
      errorMessages: { required: '...' },
    })
    
    // AFTER (CORRECT):
    yesNoUI('Are you a patient in a nursing home?')
    \`\`\``,
    
            radioSchema: `## Fix: radioSchema Function Call
    
    **Problem:** radioSchema used as bare reference instead of being called
    
    **Solution:** Call it with enum values
    
    \`\`\`javascript
    // BEFORE (WRONG):
    properties: {
      radioButtonList: radioSchema,
    }
    
    // AFTER (CORRECT):
    properties: {
      radioButtonList: radioSchema(['option1', 'option2', 'option3']),
    }
    \`\`\`
    
    **Note:** checkboxSchema is used directly (not called) - it's already a plain schema object.`,
    
            apostrophes: `## Fix: Apostrophe Syntax
    
    **Problem:** Single quotes containing apostrophes cause syntax errors
    
    **Solution:** Use double quotes or JSX expressions
    
    \`\`\`javascript
    // BEFORE (SYNTAX ERROR):
    formTitle: 'Report pension or parents' DIC eligibility'
    
    // AFTER (CORRECT - Option 1):
    formTitle: "Report pension or Parents' DIC eligibility"
    
    // AFTER (CORRECT - Option 2):
    <strong>{"If you're reporting changes after a spouse's death,"}</strong>
    \`\`\``,
    
            transformers: `## Fix: Submit Transformer
    
    **Problem:** Wrong return format, missing helpers, uses moment library
    
    **Solution:** Follow 21P-601 pattern
    
    \`\`\`javascript
    // WRONG:
    import moment from 'moment';
    return { form: JSON.stringify(result) };
    
    // CORRECT:
    import { transformForSubmit as defaultTransformForSubmit } from 'platform/forms-system/src/js/helpers';
    
    export default function submitTransformer(formConfig, form) {
      const transformedData = JSON.parse(defaultTransformForSubmit(formConfig, form));
    
      // Helper functions from 21P-601
      const splitDate = dateString => { /* ... */ };
      const formatName = nameObj => { /* ... */ };
      const formatAddress = addressObj => { /* ... */ };
    
      const result = { /* transform data */ };
    
      return JSON.stringify(result);  // Direct string return
    }
    \`\`\``,
    
            fullNamePath: `## Fix: fullNamePath in preSubmitInfo
    
    **Problem:** Missing fullNamePath prevents signature field on review page
    
    **Solution:** Add fullNamePath to statementOfTruth
    
    \`\`\`javascript
    // BEFORE (WRONG - No signature field):
    preSubmitInfo: {
      statementOfTruth: {
        body: 'I certify that the information in this form is accurate...',
      },
    }
    
    // AFTER (CORRECT - Enables signature):
    preSubmitInfo: {
      statementOfTruth: {
        body: 'I certify that the information in this form is accurate...',
        messageAriaDescribedby: 'I certify that the information in this form is accurate...',
        fullNamePath: 'veteranFullName',  // CRITICAL - path to name field
      },
    }
    \`\`\`
    
    **This is CRITICAL** - without fullNamePath, the signature field won't appear on the review page!`,
          };
    
          const content = fix_type === 'all'
            ? Object.values(fixes).join('\n\n---\n\n')
            : fixes[fix_type] || 'Fix type not found';
    
          return {
            content: [
              {
                type: 'text',
                text: content,
              },
            ],
          };
        }
  • index.js:120-133 (registration)
    The 'get_fix_reference' tool registration within the ListToolsRequestSchema handler, including its input schema defining the allowed 'fix_type' values.
      name: 'get_fix_reference',
      description: 'Get quick reference for common fixes',
      inputSchema: {
        type: 'object',
        properties: {
          fix_type: {
            type: 'string',
            enum: ['yesNoUI', 'radioSchema', 'apostrophes', 'transformers', 'fullNamePath', 'all'],
            description: 'Type of fix to get reference for',
          },
        },
        required: ['fix_type'],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Get quick reference' suggests a read-only operation, but the description doesn't clarify what format the reference takes (text, structured data, examples), whether it's cached, if there are rate limits, or what happens with the 'all' option. Minimal behavioral context is provided beyond the basic operation.

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

Conciseness4/5

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

The description is extremely concise at just 6 words, which is appropriate for a simple lookup tool. It's front-loaded with the core purpose. However, it's arguably too terse given the lack of context about what 'fixes' and 'reference' mean in this domain.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description is incomplete. It doesn't explain what constitutes a 'fix' in this context, what format the reference takes, or what value this provides compared to sibling tools. The agent must guess the tool's role in the broader system of form/prompt tools.

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% with a well-documented enum parameter, so the schema already provides complete parameter documentation. The description doesn't add any meaning beyond what the schema provides - it doesn't explain what 'fixes' are, what the reference contains, or how different fix_type values affect the output. Baseline 3 is appropriate when schema does the heavy lifting.

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

Purpose3/5

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

The description 'Get quick reference for common fixes' states a general purpose but lacks specificity about what resource is being referenced or what 'fixes' means in this context. It doesn't distinguish this tool from its siblings (audit_form, generate_orchestration_prompt, get_agent_prompt, validate_form) which all seem to relate to forms/prompts/validation. The description is vague rather than tautological.

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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention any prerequisites, context for usage, or relationship to sibling tools. The agent must infer usage from the tool name and parameter alone.

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