Skip to main content
Glama

get_visa_paths

Retrieve work visa options for each country, including visa types, costs, timelines, and sponsorship requirements to hire foreign employees.

Instructions

Work visa / right-to-work paths per country for hiring foreigners. Visa types, cost, timeline, sponsorship requirements.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYes

Implementation Reference

  • src/main.ts:711-714 (registration)
    Tool registration: defines name, description, and inputSchema for 'get_visa_paths'
      name: "get_visa_paths",
      description: "Work visa / right-to-work paths per country for hiring foreigners. Visa types, cost, timeline, sponsorship requirements.",
      inputSchema: { type: "object", properties: { country: { type: "string", enum: Object.keys(COUNTRY_BRIEFS) } }, required: ["country"] }
    },
  • Handler implementation: extracts country from args, looks up COUNTRY_BRIEFS, returns a hardcoded visaInfo map with types, cost, timeline, and sponsorship details per country.
    case "get_visa_paths": {
      const country = args?.country as string;
      const brief = COUNTRY_BRIEFS[country];
      if (!brief) throw new Error(`Unknown country: ${country}`);
      const visaInfo: Record<string, any> = {
        uk: { types: ["Skilled Worker visa", "Global Talent", "Health & Care Worker"], sponsor_licence_required: true, cost_usd: "$1.5K-5K + IHS surcharge", timeline: "3-8 weeks" },
        ireland: { types: ["Critical Skills Employment Permit", "General Employment Permit"], sponsor_licence_required: false, cost_usd: "$1K-2K", timeline: "4-12 weeks" },
        germany: { types: ["EU Blue Card", "Skilled Workers visa", "Job Seeker visa"], sponsor_licence_required: false, cost_usd: "$200-500", timeline: "8-16 weeks" },
        france: { types: ["Talent Passport", "Salaried Worker visa"], sponsor_licence_required: false, cost_usd: "$300-1K", timeline: "8-12 weeks" },
        spain: { types: ["Highly Qualified Professional", "Standard work visa"], sponsor_licence_required: false, cost_usd: "$200-500", timeline: "6-12 weeks" },
        netherlands: { types: ["Highly Skilled Migrant", "ICT permit", "DAFT (US/Japan citizens)"], sponsor_licence_required: true, cost_usd: "$500-2K", timeline: "4-8 weeks" },
        nordics: { types: ["Skilled Worker visa per country (Sweden, Norway, Denmark, Finland have separate)"], sponsor_licence_required: false, cost_usd: "$200-1K per country", timeline: "8-12 weeks" },
        mexico: { types: ["Temporary Resident visa with work permit", "INM permit"], sponsor_licence_required: true, cost_usd: "$400-1.5K", timeline: "8-16 weeks" },
        brazil: { types: ["Temporary Visa V (work)", "Permanent Visa"], sponsor_licence_required: true, cost_usd: "$500-2K", timeline: "10-20 weeks" },
        india: { types: ["Employment Visa (E)", "Project Visa"], sponsor_licence_required: true, cost_usd: "$200-500", timeline: "4-8 weeks" },
        japan: { types: ["Highly Skilled Professional", "Engineer/Specialist", "Intra-company Transferee"], sponsor_licence_required: true, cost_usd: "$300-1K", timeline: "4-12 weeks" },
        singapore: { types: ["Employment Pass", "S Pass", "Tech.Pass", "ONE Pass"], sponsor_licence_required: true, cost_usd: "$500-2K", timeline: "1-4 weeks (fastest in this list)" }
      };
      return {
        content: [{
          type: "text", text: JSON.stringify({
            module: "Visa & Right-to-Work Paths",
            country: brief.market,
            ...visaInfo[country],
            note: "EOR providers handle visa sponsorship as part of their service in countries where they have entities."
          }, null, 2)
        }]
      };
    }
Behavior3/5

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

With no annotations, the description carries full behavioral disclosure. It identifies the tool as a read operation that returns visa types, cost, timeline, and sponsorship requirements. However, it omits details like data source, recency, response format, or any limitations, leaving some behavioral gaps.

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 12-word sentence that conveys the essential purpose and outputs without any extraneous text. It is well front-loaded and efficient.

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?

No output schema is provided, but the description lists key return elements (visa types, cost, timeline, sponsorship). For a tool with one parameter and a straightforward purpose, this is sufficiently complete, though it could specify the response structure more explicitly.

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

Parameters2/5

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

The input schema has 0% description coverage, and the description only says 'per country' without adding meaning to the country parameter. It does not explain the enum values, country-specific nuances, or how the parameter affects the output.

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 provides work visa/right-to-work paths per country, listing specific outputs like visa types, cost, timeline, sponsorship requirements. This verb+resource combination effectively distinguishes it from sibling tools (e.g., EOR, termination rules).

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

Usage Guidelines3/5

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

The description implies usage for hiring foreigners and obtaining visa info, but it does not explicitly state when to use this tool over alternatives like get_country_eor_brief. No when-not-to-use guidance or comparison is provided.

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/closermethod/eor-compliance-mcp'

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