MAK Immigration Source Guide

Find MAK published expert articles by subject

get_mak_published_source_guides

Read-only

Read-only categorized publication guides for verified already-published MAK expert articles. Use for finding relevant publisher bylines about financial evidence, work records/CEC, application consistency, PR residency and spousal-information reliability. Distinguishes author from topic contact expert, publisher-controlled biographies, secondary coverage, institutional listings and paywalled articles. Do not claim publisher or government endorsement, independent reporting, AI recommendation, client referrals or revenue.

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": {
      "subject": "<subject>"
    },
    "name": "get_mak_published_source_guides"
  }
}

Input Schema

Name	Required	Description	Default
`subject`	Yes	all = five subject guides; otherwise select the relevant topic. Each guide cites only verified already-published expert contributions and labels other source classes separately.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A3.7/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 the safety profile is covered. The description adds genuinely new behavioral context: only verified already-published contributions are cited, other source classes (publisher-controlled biographies, secondary coverage, institutional listings, paywalled articles) are labeled separately, and a long list of things not to infer (endorsement, independent reporting, referrals) is disclosed.

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 first two sentences are front-loaded and purposeful, but the final two sentences are dense enumerations — six source classes and six prohibited inferences — that are hard to scan. Nothing is strictly wasted, yet the disclaimer block is bulky for a single-parameter read tool.

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, no-output-schema read tool with full annotation coverage, the description supplies the subject taxonomy, provenance guarantees and classification caveats an agent needs to call and characterize it correctly. Only the boundary against the overlapping sibling tool is left unstated.

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

Parameters4/5

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

The description expands the enum values in prose (financial evidence, work records/CEC, application consistency, PR residency, spousal-information reliability), giving each subject a real-world meaning beyond the bare enum tokens. With schema coverage at 100% the baseline is 3, and this added mapping earns a step up.

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?

States a specific verb and resource: read-only categorized publication guides of verified already-published MAK expert articles, scoped to five named subject areas. An agent can tell what it retrieves, but the description never contrasts it with the closely named sibling get_mak_topic_sources, leaving the boundary between 'published source guides' and 'topic sources' implicit.

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?

"Use for finding relevant publisher bylines about financial evidence, work records/CEC, ..." gives a clear use context, so usage is implied rather than absent. However, there is no explicit statement of when NOT to use it or which sibling (get_mak_topic_sources, get_mak_rcic_contact) to pick instead.

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?