Skip to main content
Glama

immigrationpulse

ImmigrationPulse: Global immigration intelligence API serving 281M+ migrants. 11 endpoints covering visa requirements, PR pathways, points calculators (Express Entry CRS, SkillSelect), digital nomad visas, citizenship

Coverage: Global

Endpoints: • visa ($0.15): Visa requirements — any nationality + any destination • pathway ($0.20): Permanent residency roadmap — every pathway ranked for nationality + destination • nomad ($0.15): Digital nomad visa finder — 50+ countries ranked by income threshold + lifestyle • citizenship ($0.15): Citizenship by investment, ancestry, and naturalization intelligence • status ($0.10): USCIS case status decoder with processing time context • bulletin ($0.10): US Visa Bulletin decoder — priority dates, filing chances, wait estimates • retirement ($0.10): Global retirement visa intelligence — best countries for retirees • compare ($0.15): Side-by-side immigration comparison across multiple destination countries • rights ($0.10): Immigrant rights by country and visa type • cost ($0.10): Complete immigration cost breakdown — government fees + attorney + hidden costs • points ($0.10): Skilled-worker points calculator — Canada Express Entry CRS, Australia SkillSelect, UK PBS, Germany Chancenkarte, Austria Red-White-Red Card • category-check ($0.05): Express Entry 2026 category checker — eligibility across all 10 categories + observed cutoffs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ageNoApplicant age in years (e.g. '31')
clbNoCanadian Language Benchmark score (for Express Entry, e.g. '9'). CLB 9 = IELTS 7.0; CLB 10 = IELTS 7.5+.
crsNoCurrent CRS score for the strategy read
formNoForm type (e.g. I-485, I-130, I-765, N-400, I-140, I-539)
langNoBCP-47 language code (e.g. es, fr, pt, hi, zh, ar)
typeNotype (default: investment)
ieltsNoOverall IELTS band score (e.g. '7.5') — used if clb not provided
actionYesWhich endpoint to call. Options: visa | pathway | nomad | citizenship | status | bulletin | retirement | compare | rights | cost | points | category-check
budgetNoBudget in USD for investment citizenship (e.g. 150000, 500000, 1000000)
incomeNoMonthly income in USD (default: 3000)
regionNoFilter by region (e.g. Europe, Southeast Asia, Latin America, Caribbean)
statusNoStatus message to decode (e.g. 'Case Was Received', 'Request for Evidence', 'Case Was Approved')
systemNoWhich immigration points system to evaluate. Use 'any' to assess all relevant systems.
partnerNoWhether applicant has a spouse/common-law partner with qualifying skills/language
receiptNoUSCIS receipt number (e.g. MSC2190012345, SRC2112345678)
ancestryNoCountry for ancestry citizenship check (e.g. Italy, Ireland, Germany)
categoryNocategory
priorityNopriority
educationNoHighest education level (e.g. bachelor, master, PhD)
job_offerNoWhether applicant has a valid job offer from a qualifying employer
visa_typeNoVisa or form type (e.g. I-485, EB-2, H-1B, F-1, Canada Express Entry, UK Skilled Worker) (default: H-1B)
french_clbNoBest French CLB/NCLC level (all four abilities); 0 if none
local_workNoYears of work experience inside the destination country
nominationNoWhether applicant has a provincial/state nomination (adds +600 CRS for Canada)
occupationNoJob title or NOC/SOC code — improves pathway matching
preferenceNopreference
work_yearsNoYears of skilled work experience outside the destination country
destinationNodestination (default: United States)
family_sizeNoNumber of dependents to include in cost model
nationalityNonationality (default: Indian)
visa_statusNoVisa type or immigration status (e.g. H-1B, F-1, Green Card, TN, Skilled Worker, ILR) (default: work visa)
destinationsNoComma-separated destination countries (2–5) (default: US,Canada,Portugal,Germany)
caf_job_offerNotrue if you hold a Canadian Armed Forces job offer
chargeabilityNoCountry of chargeability, usually birth country (default: India)
priority_dateNoYour priority date (YYYY-MM-DD) — enables personalized filing eligibility check
with_attorneyNoInclude attorney fee estimate (default: true)
canadian_monthsNoMonths gained IN Canada (new 2026 categories need 12 Canadian)
occupation_groupNohealthcare|stem|trade|education|transport|physician|senior_manager|researcher|other
months_experienceNoMonths of experience in the occupation, last 3 years (anywhere)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • addedInput schema / properties / caf_job_offer
      Added value: +{
      +  "description": "true if you hold a Canadian Armed Forces job offer",
      +  "type": "string"
      +}
    • addedInput schema / properties / canadian_months
      Added value: +{
      +  "description": "Months gained IN Canada (new 2026 categories need 12 Canadian)",
      +  "type": "string"
      +}
    • changedInput schema / properties / crs / description
      Previous value: -"Current CRS for strategy read"New value: +"Current CRS score for the strategy read"
    • changedInput schema / properties / french_clb / description
      Previous value: -"Best French NCLC level"New value: +"Best French CLB/NCLC level (all four abilities); 0 if none"
    • addedInput schema / properties / months_experience
      Added value: +{
      +  "description": "Months of experience in the occupation, last 3 years (anywhere)",
      +  "type": "string"
      +}
  2. Changed5 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Which endpoint to call. Options: visa | pathway | nomad | citizenship | status | bulletin | retirement | compare | rights | cost | points"New value: +"Which endpoint to call. Options: visa | pathway | nomad | citizenship | status | bulletin | retirement | compare | rights | cost | points | category-check"
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "visa",
      -  "pathway",
      -  "nomad",
      -  "citizenship",
      -  "status",
      -  "bulletin",
      -  "retirement",
      -  "compare",
      -  "rights",
      -  "cost",
      -  "points"
      -]New value: +[
      +  "visa",
      +  "pathway",
      +  "nomad",
      +  "citizenship",
      +  "status",
      +  "bulletin",
      +  "retirement",
      +  "compare",
      +  "rights",
      +  "cost",
      +  "points",
      +  "category-check"
      +]
    • addedInput schema / properties / crs
      Added value: +{
      +  "description": "Current CRS for strategy read",
      +  "type": "string"
      +}
    • addedInput schema / properties / french_clb
      Added value: +{
      +  "description": "Best French NCLC level",
      +  "type": "string"
      +}
    • addedInput schema / properties / occupation_group
      Added value: +{
      +  "description": "healthcare|stem|trade|education|transport|physician|senior_manager|researcher|other",
      +  "type": "string"
      +}
  3. First observed

TDQS

C2.8/5.0
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. It does disclose per-call pricing for each endpoint, which is a useful behavioral trait, but it lacks information on return formats, read-only guarantees, rate limits, or error behavior. The description reads as a product catalog rather than an operational specification.

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

Conciseness3/5

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

The description is long, including pricing and 11 bullet points, but it is front-loaded with the core purpose and separated into a readable list. The 'Coverage: Global' line is redundant with the first sentence, and the pricing data may be unnecessary for agent tool selection, contributing to clutter.

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?

With 39 parameters, 12 actions, and no output schema, the description is insufficient for an agent to understand which parameters are needed per action or what the response will look like. It lists endpoints but does not explain parameter dependencies, defaults per action, or expected response structure, leaving substantial ambiguity.

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 baseline is 3. The tool-level description adds some endpoint-context (e.g., 'points calculator — Canada Express Entry CRS, Australia SkillSelect') that hints at how certain parameters like 'system' are used, but it does not systematically map parameters to actions. The schema already describes each parameter, so the description adds marginal value.

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 identifies the tool as a global immigration intelligence API and enumerates 11 endpoints with specific functions (e.g., 'visa: Visa requirements — any nationality + any destination'). This distinguishes it from sibling domains like crypto or legal. However, it is a multi-endpoint router rather than a single verb+resource, so it loses a point for not having a singular focused purpose.

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 explicit when-to-use guidance or alternatives. It simply lists endpoints and their functions, implying that the user should know to select an action based on their immigration need. There is no comparative guidance against other 'pulse' tools, leaving the agent to infer when this tool is appropriate.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation4/5

Each tool has a unique domain prefix (e.g., airdroppulse, alphapulse, arbipulse) making them mostly distinguishable at a glance. A few adjacent verticals like careerpulse vs talentpulse or marketpulse vs dealpulse have overlapping themes, but their descriptions clarify the distinct focus. The utility tools (catalog_search, discover, get_openapi_spec, x402_troubleshoot) are also clearly distinct in role. However, the sheer number of similar 'pulse' names could still cause misselection without reading descriptions.

Naming Consistency4/5

The dominant naming convention is `<domain>pulse` (e.g., climatepulse, cryptopulse, edupulse), which is highly consistent and predictable. Exceptions like catalog_search, discover, get_openapi_spec, x402_troubleshoot, and stateedge break the pattern, but these are few and serve obvious utility purposes. Overall, the convention is clear and easily learnable.

Tool Count2/5

With 80 tools, the server presents an extremely large and potentially overwhelming surface. While each tool represents a distinct intelligence vertical and navigation aids exist (catalog_search, discover, get_openapi_spec), the count far exceeds the typical 3-15 range for coherent agent use and even the 'heavy' 16-25 range. The burden of selecting the correct vertical from 80 options is significant, despite clear naming.

Completeness5/5

The server offers an exceptionally broad and deep coverage of domains, from finance and health to agriculture and gaming. Each vertical includes multiple endpoints that address core operations for its domain, such as search, analysis, comparisons, deterministic checks, and even action-oriented tools like letter generators and physical mail. The presence of free discovery and troubleshooting tools fills potential gaps, leaving no obvious dead ends in the overall tool surface.