Skip to main content
Glama
Jazib-but

VAT Validation MCP Server

by Jazib-but

list_eu_member_states

Retrieve all EU member state codes required for validating VAT numbers through the official VIES service.

Instructions

List all EU member state codes for VAT validation / Zobraziť všetky kódy členských štátov EÚ pre validáciu IČ DPH

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler that maps EU_MEMBER_STATES to bilingual names and returns formatted text list.
    case 'list_eu_member_states': {
      const memberStates = EU_MEMBER_STATES.map(code => {
        const countryNames: Record<string, string> = {
          'AT': 'Austria / Rakúsko',
          'BE': 'Belgium / Belgicko',
          'BG': 'Bulgaria / Bulharsko',
          'CY': 'Cyprus / Cyprus',
          'CZ': 'Czech Republic / Česká republika',
          'DE': 'Germany / Nemecko',
          'DK': 'Denmark / Dánsko',
          'EE': 'Estonia / Estónsko',
          'EL': 'Greece / Grécko',
          'ES': 'Spain / Španielsko',
          'FI': 'Finland / Fínsko',
          'FR': 'France / Francúzsko',
          'HR': 'Croatia / Chorvátsko',
          'HU': 'Hungary / Maďarsko',
          'IE': 'Ireland / Írsko',
          'IT': 'Italy / Taliansko',
          'LT': 'Lithuania / Litva',
          'LU': 'Luxembourg / Luxembursko',
          'LV': 'Latvia / Lotyšsko',
          'MT': 'Malta / Malta',
          'NL': 'Netherlands / Holandsko',
          'PL': 'Poland / Poľsko',
          'PT': 'Portugal / Portugalsko',
          'RO': 'Romania / Rumunsko',
          'SE': 'Sweden / Švédsko',
          'SI': 'Slovenia / Slovinsko',
          'SK': 'Slovakia / Slovensko',
        };
        return `${code}: ${countryNames[code] || code}`;
      });
    
      return {
        content: [
          {
            type: 'text',
            text: `EU Member States for VAT Validation / Členské štáty EÚ pre validáciu IČ DPH:\n\n${memberStates.join('\n')}`,
          },
        ],
      };
    }
  • src/index.ts:84-91 (registration)
    Tool registration in ListToolsRequestSchema handler, including name, description, and empty input schema.
    {
      name: 'list_eu_member_states',
      description: 'List all EU member state codes for VAT validation / Zobraziť všetky kódy členských štátov EÚ pre validáciu IČ DPH',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Constant array of EU member state codes used by the handler.
    export const EU_MEMBER_STATES = [
      'AT', 'BE', 'BG', 'CY', 'CZ', 'DE', 'DK', 'EE', 'EL', 'ES', 'FI', 'FR',
      'HR', 'HU', 'IE', 'IT', 'LT', 'LU', 'LV', 'MT', 'NL', 'PL', 'PT', 'RO',
      'SE', 'SI', 'SK'
    ] as const;
Behavior3/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. It describes the tool's behavior as listing codes, which is straightforward, but does not disclose additional traits like rate limits, authentication needs, or output format. For a simple read-only tool with no parameters, this is adequate but minimal.

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 highly concise and front-loaded, consisting of a single, efficient sentence in two languages that directly states the tool's purpose. Every word earns its place, with no wasted information, making it easy to understand quickly.

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

Completeness4/5

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

Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is complete enough for its purpose. It clearly explains what the tool does and its use case. However, it could be slightly enhanced by mentioning the output format (e.g., list of codes) to improve completeness, though this is minor.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter details, which is appropriate. A baseline of 4 is applied for zero parameters, as the description effectively covers the tool's scope without unnecessary parameter information.

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

Purpose5/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 ('List') and resource ('EU member state codes'), and it distinguishes this from sibling tools by specifying it's for listing codes rather than checking/validating VAT numbers like the siblings (check_vat_number, check_vat_test_service, check_vies_status). The bilingual phrasing adds clarity without redundancy.

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

Usage Guidelines4/5

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

The description explicitly states when to use this tool ('for VAT validation'), providing clear context. However, it does not specify when not to use it or name alternatives among the sibling tools, though the purpose differentiation implies usage scenarios. This is sufficient for clear guidance but lacks explicit exclusions.

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/Jazib-but/check-vat-vies-mcp-Jazib'

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