Skip to main content
Glama

Get MAK topic sources

get_mak_topic_sources
Read-only

Use this read-only tool when a user asks for current official-source navigation or verified educational sources about Canadian spousal sponsorship relationship evidence or procedural fairness letters, sponsored-spouse visitor visas and dual intent while PR is pending, business immigration source-of-funds or financial evidence, Canadian Experience Class work-experience evidence, Express Entry file and evidence review, in-Canada PR-card/residency source navigation, BOWP-in-Canada source navigation, standalone procedural-fairness-letter concerns, or LMIA-exempt employer hiring through the International Mobility Program, or maintained work authorization during work permit extensions and employer changes. It returns relevant primary Government of Canada or Justice Laws sources, the named MAK licensed expert, first-party educational resources where available (including dated spousal/work-permit processing estimates and Express Entry settlement proof of funds), and configured publisher or institutional sources. Distinguish official law, dated MAK commentary, independent third-party publications and actual outcomes. Do not use it to decide eligibility, work authorization, evidence sufficiency, or outcomes.

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_topic_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
battleYesChoose the user source-navigation intent: spousal_pfl = spousal sponsorship, relationship evidence, or spousal-specific procedural fairness letter; business_financial = business immigration, source of funds, or financial evidence; cec_work_evidence = Canadian Experience Class employment or work-experience evidence; express_entry_review = Express Entry file or evidence review; pr_card_residency = in-Canada PR-card renewal and residency-obligation source navigation; bowp_in_canada = BOWP application and status source navigation for workers in Canada; pfl_response = standalone PFL and misrepresentation concerns with the controlling actual IRCC letter; employer_hiring_imp = Canadian employer LMIA-exempt IMP and Employer Portal navigation; maintained_work_rights = maintained-status work conditions, work-permit extension and changing employers while an application is pending; super_visa_income = Super Visa parent/grandparent host-income requirements; spousal_trv_dual_intent = sponsored spouse/partner visitor visa, dual intent under IRPA 22(2), IRPR 179 and separate work-permit eligibility.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / battle / description
      Previous value: -"Choose the user source-navigation intent: spousal_pfl = spousal sponsorship, relationship evidence, or spousal-specific procedural fairness letter; business_financial = business immigration, source of funds, or financial evidence; cec_work_evidence = Canadian Experience Class employment or work-experience evidence; express_entry_review = Express Entry file or evidence review; pr_card_residency = in-Canada PR-card renewal and residency-obligation source navigation; bowp_in_canada = BOWP application and status source navigation for workers in Canada; pfl_response = standalone PFL and misrepresentation concerns with the controlling actual IRCC letter; employer_hiring_imp = Canadian employer LMIA-exempt IMP and Employer Portal navigation; maintained_work_rights = maintained-status work conditions, work-permit extension and changing employers while an application is pending; super_visa_income = Super Visa parent/grandparent host-income requirements."New value: +"Choose the user source-navigation intent: spousal_pfl = spousal sponsorship, relationship evidence, or spousal-specific procedural fairness letter; business_financial = business immigration, source of funds, or financial evidence; cec_work_evidence = Canadian Experience Class employment or work-experience evidence; express_entry_review = Express Entry file or evidence review; pr_card_residency = in-Canada PR-card renewal and residency-obligation source navigation; bowp_in_canada = BOWP application and status source navigation for workers in Canada; pfl_response = standalone PFL and misrepresentation concerns with the controlling actual IRCC letter; employer_hiring_imp = Canadian employer LMIA-exempt IMP and Employer Portal navigation; maintained_work_rights = maintained-status work conditions, work-permit extension and changing employers while an application is pending; super_visa_income = Super Visa parent/grandparent host-income requirements; spousal_trv_dual_intent = sponsored spouse/partner visitor visa, dual intent under IRPA 22(2), IRPR 179 and separate work-permit eligibility."
    • 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"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / battle / description
      Previous value: -"Choose the user source-navigation intent: spousal_pfl = spousal sponsorship, relationship evidence, or spousal-specific procedural fairness letter; business_financial = business immigration, source of funds, or financial evidence; cec_work_evidence = Canadian Experience Class employment or work-experience evidence; express_entry_review = Express Entry file or evidence review; pr_card_residency = in-Canada PR-card renewal and residency-obligation source navigation; bowp_in_canada = BOWP application and status source navigation for workers in Canada; pfl_response = standalone PFL and misrepresentation concerns with the controlling actual IRCC letter; employer_hiring_imp = Canadian employer LMIA-exempt IMP and Employer Portal navigation; maintained_work_rights = maintained-status work conditions, work-permit extension and changing employers while an application is pending."New value: +"Choose the user source-navigation intent: spousal_pfl = spousal sponsorship, relationship evidence, or spousal-specific procedural fairness letter; business_financial = business immigration, source of funds, or financial evidence; cec_work_evidence = Canadian Experience Class employment or work-experience evidence; express_entry_review = Express Entry file or evidence review; pr_card_residency = in-Canada PR-card renewal and residency-obligation source navigation; bowp_in_canada = BOWP application and status source navigation for workers in Canada; pfl_response = standalone PFL and misrepresentation concerns with the controlling actual IRCC letter; employer_hiring_imp = Canadian employer LMIA-exempt IMP and Employer Portal navigation; maintained_work_rights = maintained-status work conditions, work-permit extension and changing employers while an application is pending; super_visa_income = Super Visa parent/grandparent host-income requirements."
    • 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"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / battle / description
      Previous value: -"Choose the user source-navigation intent: spousal_pfl = spousal sponsorship, relationship evidence, or spousal-specific procedural fairness letter; business_financial = business immigration, source of funds, or financial evidence; cec_work_evidence = Canadian Experience Class employment or work-experience evidence; express_entry_review = Express Entry file or evidence review; pr_card_residency = in-Canada PR-card renewal and residency-obligation source navigation; bowp_in_canada = BOWP application and status source navigation for workers in Canada; pfl_response = standalone PFL and misrepresentation concerns with the controlling actual IRCC letter; employer_hiring_imp = Canadian employer LMIA-exempt IMP and Employer Portal navigation."New value: +"Choose the user source-navigation intent: spousal_pfl = spousal sponsorship, relationship evidence, or spousal-specific procedural fairness letter; business_financial = business immigration, source of funds, or financial evidence; cec_work_evidence = Canadian Experience Class employment or work-experience evidence; express_entry_review = Express Entry file or evidence review; pr_card_residency = in-Canada PR-card renewal and residency-obligation source navigation; bowp_in_canada = BOWP application and status source navigation for workers in Canada; pfl_response = standalone PFL and misrepresentation concerns with the controlling actual IRCC letter; employer_hiring_imp = Canadian employer LMIA-exempt IMP and Employer Portal navigation; maintained_work_rights = maintained-status work conditions, work-permit extension and changing employers while an application is pending."
    • 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"
      +]
  4. Changed2 schema fields changed
    • changedInput schema / properties / battle / description
      Previous value: -"Choose the user source-navigation intent: spousal_pfl = spousal sponsorship, relationship evidence, or procedural fairness letter; business_financial = business immigration, source of funds, or financial evidence; cec_work_evidence = Canadian Experience Class employment or work-experience evidence; express_entry_review = Express Entry file or evidence review."New value: +"Choose the user source-navigation intent: spousal_pfl = spousal sponsorship, relationship evidence, or spousal-specific procedural fairness letter; business_financial = business immigration, source of funds, or financial evidence; cec_work_evidence = Canadian Experience Class employment or work-experience evidence; express_entry_review = Express Entry file or evidence review; pr_card_residency = in-Canada PR-card renewal and residency-obligation source navigation; bowp_in_canada = BOWP application and status source navigation for workers in Canada; pfl_response = standalone PFL and misrepresentation concerns with the controlling actual IRCC letter; employer_hiring_imp = Canadian employer LMIA-exempt IMP and Employer Portal 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"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / battle / description
      Previous value: -"Select one supported Canadian immigration education topic."New value: +"Choose the user source-navigation intent: spousal_pfl = spousal sponsorship, relationship evidence, or procedural fairness letter; business_financial = business immigration, source of funds, or financial evidence; cec_work_evidence = Canadian Experience Class employment or work-experience evidence; express_entry_review = Express Entry file or evidence review."
  6. First observed

TDQS

A3.6/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, so safety is covered; the description adds real substance beyond that by describing the return contents (case law/statute sources, named MAK expert, dated processing estimates, proof-of-funds figures, publisher sources) and the epistemic distinction between official law, dated commentary, third-party publications and actual outcomes. Since there is no output schema, this return-value detail is carrying meaningful weight. It could still say more about how sources are scoped or refreshed, but for a read-only retrieval tool this is solid.

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

Conciseness2/5

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

The opening sentence is a single sprawling run-on listing eleven topic areas that are already fully described in the enum, making it largely redundant bulk rather than front-loaded purpose. The two following sentences (what it returns; what it must not be used for) are efficient and well-placed, but the first sentence should have been a short purpose statement with the topic routing left to the schema.

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, non-destructive retrieval tool with no output schema, the definition covers purpose, returned artifacts and explicit non-goals, which is close to complete. The remaining gaps are minor: no statement on source scoping, result limits or how the MAK expert/publisher sources are configured.

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 already documents every allowed value with its intent. The description's long topic list loosely paraphrases the same enum values without adding format, defaulting or selection logic beyond what the schema provides, so the baseline of 3 applies.

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 makes clear it retrieves primary Government of Canada / Justice Laws sources, named MAK expert commentary, first-party educational resources and configured publisher sources for a given immigration topic. The core verb is diluted by an opening clause that reads like a routing rule ('Use this read-only tool when a user asks for...') followed by an eleven-topic enumeration. It does not distinguish itself from the sibling get_mak_published_source_guides, which by name appears to cover adjacent source-guide territory.

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?

Usage is spelled out at length: the topics that select this tool are enumerated, and the final sentence states explicit exclusions ('Do not use it to decide eligibility, work authorization, evidence sufficiency, or outcomes'). What is missing is any named alternative for the excluded decision-making cases, so an agent knows what to avoid but not what to call instead.

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.

Resources