Skip to main content
Glama

immigrationpulse

Check visa requirements, permanent residency pathways, and points scores for skilled workers. Find citizenship options, USCIS case status, and compare immigration costs.

Instructions

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

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+.
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
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
budgetNoBudget in USD for investment citizenship (e.g. 150000, 500000, 1000000)
incomeNoMonthly income in USD
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)
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
family_sizeNoNumber of dependents to include in cost model
nationalityNonationality
visa_statusNoVisa type or immigration status (e.g. H-1B, F-1, Green Card, TN, Skilled Worker, ILR)
destinationsNoComma-separated destination countries (2–5)
chargeabilityNoCountry of chargeability (usually birth country)
priority_dateNoYour priority date (YYYY-MM-DD) — enables personalized filing eligibility check
with_attorneyNoInclude attorney fee estimate (default: true)
Behavior2/5

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

No annotations provided. The description mentions pricing per endpoint but does not disclose behavioral traits such as authentication needs, rate limits, error responses, or side effects. Given the lack of annotations, the description fails to compensate.

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 well-structured with bullet points but is verbose (multiple paragraphs). It could be more concise by focusing on the core routing mechanism and reducing extraneous pricing details.

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 complex tool with 11 sub-actions and 33 parameters, the description is incomplete. It does not map parameters to endpoints, explain output format, or handle error scenarios. An AI agent lacks sufficient context to use it effectively.

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?

Schema coverage is 100%, but the description adds little beyond the schema. Many parameter descriptions in the schema are terse (e.g., 'destination' as just 'destination'), and the tool description does not explain how parameters interact with specific endpoints or add usage context.

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 identifies the tool as an immigration intelligence API and lists 11 endpoints, but it does not succinctly state that the tool is an endpoint router selected by the 'action' parameter. The purpose is clear but could be more focused for an AI agent.

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 on when to use this tool versus sibling tools (e.g., alphapulse, travelpulse) or when to avoid it. The description lists endpoints but does not provide decision criteria or context for selection.

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/GTCC777/mcp-pulsenetwork'

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