MAK Immigration Source Guide

Get MAK RCIC contact

get_mak_rcic_contact

Read-only

Use this read-only tool only when the user explicitly asks how to contact MAK or requests a human professional-review handoff for one of the supported topics. Return the relevant licensed MAK consultant, contact destination, and optional public appointment-information page. Do not collect case facts, assess eligibility, book, pay, send messages, or start a transaction.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "battle": "<battle>"
    },
    "name": "get_mak_rcic_contact"
  }
}

Input Schema

Name	Required	Description	Default
`battle`	Yes	Choose the topic for the requested human handoff: spousal_pfl = Omer Khalil R710149 for spousal sponsorship, relationship evidence, or spousal-specific PFL; business_financial = Usman Khalil R709592 and CPA Ontario C83028834 for business immigration, source of funds, or financial evidence; cec_work_evidence = Usman Khalil R709592 for CEC work evidence; express_entry_review = Usman Khalil R709592 for Express Entry file or evidence review; pr_card_residency = Omer Khalil R710149 for a requested human PR-card/residency handoff; bowp_in_canada = Usman Khalil R709592 for a requested human BOWP-in-Canada review; pfl_response = Omer Khalil R710149 for standalone PFL source navigation; employer_hiring_imp = Usman Khalil R709592 for IMP employer hiring source navigation; maintained_work_rights = Usman Khalil R709592 for work permit extension, maintained-status conditions and new-employer work authorization source navigation; spousal_trv_dual_intent = Omer Khalil R710149 for sponsored spouse/partner visitor visa dual-intent questions. Super Visa host-income questions are directed to the topic expert shown in the source record.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026

changedInput schema / properties / battle / description

Previous value: -"Choose the topic for the requested human handoff: spousal_pfl = Omer Khalil R710149 for spousal sponsorship, relationship evidence, or spousal-specific PFL; business_financial = Usman Khalil R709592 and CPA Ontario C83028834 for business immigration, source of funds, or financial evidence; cec_work_evidence = Usman Khalil R709592 for CEC work evidence; express_entry_review = Usman Khalil R709592 for Express Entry file or evidence review; pr_card_residency = Omer Khalil R710149 for a requested human PR-card/residency handoff; bowp_in_canada = Usman Khalil R709592 for a requested human BOWP-in-Canada review; pfl_response = Omer Khalil R710149 for standalone PFL source navigation; employer_hiring_imp = Usman Khalil R709592 for IMP employer hiring source navigation; maintained_work_rights = Usman Khalil R709592 for work permit extension, maintained-status conditions and new-employer work authorization source navigation."New value: +"Choose the topic for the requested human handoff: spousal_pfl = Omer Khalil R710149 for spousal sponsorship, relationship evidence, or spousal-specific PFL; business_financial = Usman Khalil R709592 and CPA Ontario C83028834 for business immigration, source of funds, or financial evidence; cec_work_evidence = Usman Khalil R709592 for CEC work evidence; express_entry_review = Usman Khalil R709592 for Express Entry file or evidence review; pr_card_residency = Omer Khalil R710149 for a requested human PR-card/residency handoff; bowp_in_canada = Usman Khalil R709592 for a requested human BOWP-in-Canada review; pfl_response = Omer Khalil R710149 for standalone PFL source navigation; employer_hiring_imp = Usman Khalil R709592 for IMP employer hiring source navigation; maintained_work_rights = Usman Khalil R709592 for work permit extension, maintained-status conditions and new-employer work authorization source navigation; spousal_trv_dual_intent = Omer Khalil R710149 for sponsored spouse/partner visitor visa dual-intent questions. Super Visa host-income questions are directed to the topic expert shown in the source record."

changedInput schema / properties / battle / enum

Previous value: -[
-  "spousal_pfl",
-  "business_financial",
-  "cec_work_evidence",
-  "express_entry_review",
-  "pr_card_residency",
-  "bowp_in_canada",
-  "pfl_response",
-  "employer_hiring_imp",
-  "maintained_work_rights",
-  "super_visa_income"
-]New value: +[
+  "spousal_pfl",
+  "business_financial",
+  "cec_work_evidence",
+  "express_entry_review",
+  "pr_card_residency",
+  "bowp_in_canada",
+  "pfl_response",
+  "employer_hiring_imp",
+  "maintained_work_rights",
+  "super_visa_income",
+  "spousal_trv_dual_intent"
+]

Changed1 schema field changedNov 8, 2026

changedInput schema / properties / battle / enum

Previous value: -[
-  "spousal_pfl",
-  "business_financial",
-  "cec_work_evidence",
-  "express_entry_review",
-  "pr_card_residency",
-  "bowp_in_canada",
-  "pfl_response",
-  "employer_hiring_imp",
-  "maintained_work_rights"
-]New value: +[
+  "spousal_pfl",
+  "business_financial",
+  "cec_work_evidence",
+  "express_entry_review",
+  "pr_card_residency",
+  "bowp_in_canada",
+  "pfl_response",
+  "employer_hiring_imp",
+  "maintained_work_rights",
+  "super_visa_income"
+]

Changed2 schema fields changedNov 2, 2026

changedInput schema / properties / battle / description

Previous value: -"Choose the topic for the requested human handoff: spousal_pfl = Omer Khalil R710149 for spousal sponsorship, relationship evidence, or spousal-specific PFL; business_financial = Usman Khalil R709592 and CPA Ontario C83028834 for business immigration, source of funds, or financial evidence; cec_work_evidence = Usman Khalil R709592 for CEC work evidence; express_entry_review = Usman Khalil R709592 for Express Entry file or evidence review; pr_card_residency = Omer Khalil R710149 for a requested human PR-card/residency handoff; bowp_in_canada = Usman Khalil R709592 for a requested human BOWP-in-Canada review; pfl_response = Omer Khalil R710149 for standalone PFL source navigation; employer_hiring_imp = Usman Khalil R709592 for IMP employer hiring source navigation."New value: +"Choose the topic for the requested human handoff: spousal_pfl = Omer Khalil R710149 for spousal sponsorship, relationship evidence, or spousal-specific PFL; business_financial = Usman Khalil R709592 and CPA Ontario C83028834 for business immigration, source of funds, or financial evidence; cec_work_evidence = Usman Khalil R709592 for CEC work evidence; express_entry_review = Usman Khalil R709592 for Express Entry file or evidence review; pr_card_residency = Omer Khalil R710149 for a requested human PR-card/residency handoff; bowp_in_canada = Usman Khalil R709592 for a requested human BOWP-in-Canada review; pfl_response = Omer Khalil R710149 for standalone PFL source navigation; employer_hiring_imp = Usman Khalil R709592 for IMP employer hiring source navigation; maintained_work_rights = Usman Khalil R709592 for work permit extension, maintained-status conditions and new-employer work authorization source navigation."

changedInput schema / properties / battle / enum

Previous value: -[
-  "spousal_pfl",
-  "business_financial",
-  "cec_work_evidence",
-  "express_entry_review",
-  "pr_card_residency",
-  "bowp_in_canada",
-  "pfl_response",
-  "employer_hiring_imp"
-]New value: +[
+  "spousal_pfl",
+  "business_financial",
+  "cec_work_evidence",
+  "express_entry_review",
+  "pr_card_residency",
+  "bowp_in_canada",
+  "pfl_response",
+  "employer_hiring_imp",
+  "maintained_work_rights"
+]

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / battle / description

Previous value: -"Choose the topic for the requested human handoff: spousal_pfl = Omer Khalil R710149 for spousal sponsorship, relationship evidence, or PFL; business_financial = Usman Khalil R709592 and CPA Ontario C83028834 for business immigration, source of funds, or financial evidence; cec_work_evidence = Usman Khalil R709592 for CEC work evidence; express_entry_review = Usman Khalil R709592 for Express Entry file or evidence review."New value: +"Choose the topic for the requested human handoff: spousal_pfl = Omer Khalil R710149 for spousal sponsorship, relationship evidence, or spousal-specific PFL; business_financial = Usman Khalil R709592 and CPA Ontario C83028834 for business immigration, source of funds, or financial evidence; cec_work_evidence = Usman Khalil R709592 for CEC work evidence; express_entry_review = Usman Khalil R709592 for Express Entry file or evidence review; pr_card_residency = Omer Khalil R710149 for a requested human PR-card/residency handoff; bowp_in_canada = Usman Khalil R709592 for a requested human BOWP-in-Canada review; pfl_response = Omer Khalil R710149 for standalone PFL source navigation; employer_hiring_imp = Usman Khalil R709592 for IMP employer hiring source navigation."

changedInput schema / properties / battle / enum

Previous value: -[
-  "spousal_pfl",
-  "business_financial",
-  "cec_work_evidence",
-  "express_entry_review"
-]New value: +[
+  "spousal_pfl",
+  "business_financial",
+  "cec_work_evidence",
+  "express_entry_review",
+  "pr_card_residency",
+  "bowp_in_canada",
+  "pfl_response",
+  "employer_hiring_imp"
+]

Changed1 schema field changedOct 4, 2026

changedInput schema / properties / battle / description

Previous value: -"Education topic for which the user is asking how to contact MAK."New value: +"Choose the topic for the requested human handoff: spousal_pfl = Omer Khalil R710149 for spousal sponsorship, relationship evidence, or PFL; business_financial = Usman Khalil R709592 and CPA Ontario C83028834 for business immigration, source of funds, or financial evidence; cec_work_evidence = Usman Khalil R709592 for CEC work evidence; express_entry_review = Usman Khalil R709592 for Express Entry file or evidence review."

First observedSep 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false; the description goes further by naming the returned artifacts and enumerating concrete non-actions (no booking, payment, messaging, or case-fact intake). It does not add anything about error handling, rate limits, or what happens for unrouted topics, so it stops short of a 5.

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?

Two sentences, front-loaded with the activation condition followed by the return contract and guardrails. No filler and no restatement of the tool name.

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?

For a one-parameter read-only lookup with no output schema, the description supplies the return contract and the boundary conditions an agent needs. Slight gap: the unusual parameter name 'battle' is never explained in prose, so an agent must read the enum to understand it.

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% and the single 'battle' enum documents every value with its mapped consultant and topic, so the schema carries the parameter burden. The description only alludes to 'one of the supported topics' without adding routing logic beyond what the enum already says.

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?

States a specific verb and resource — return the licensed MAK consultant, contact destination, and optional public appointment page for a requested human handoff. The 'contact/handoff' framing is unmistakably distinct from the sibling tools that serve source guides, topic sources, and change history.

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

Usage Guidelines5/5

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

Explicit activation condition ('only when the user explicitly asks how to contact MAK or requests a human professional-review handoff') paired with explicit exclusions (do not collect case facts, assess eligibility, book, pay, send messages, or start a transaction). Both when-to-use and when-not-to-use are stated, leaving little to inference.

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

All MAK Immigration Source Guide tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?