OathReady: Canadian Citizenship Test

Get citizenship journey timelines

get_journey_stats

Read-onlyIdempotent

How long the citizenship journey takes: the official IRCC processing time plus anonymous community medians (days from application to each milestone: AOR, test invitation, test, oath) contributed by OathReady users who share their journeys. Community cohorts under 5 journeys are never published.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`stages`	Yes
`web_page`	Yes
`community`	Yes	null until enough journeys are shared
`official_processing_time`	Yes

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate readOnly and idempotent behavior; description adds context about community contributions and privacy thresholds, complementing structured data well.

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 concise sentences front-load key information with no wasted words, earning a top score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description sufficiently explains the tool's data source and content, covering the needed context.

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?

No parameters exist, so baseline 4 applies; description correctly avoids unnecessary detail, and schema coverage is 100%.

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?

The description clearly specifies the tool provides citizenship journey timelines, including official IRCC processing time and anonymous community medians, distinguishing it from siblings like get_citizenship_stats.

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?

The description implies usage for timeline data and mentions data limitations (cohorts under 5 not published), but does not explicitly state when to use versus alternatives.

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

All OathReady: Canadian Citizenship Test tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: presence calculation, question lookup/grading, stats, daily challenge, journey stats, mock test, oath guide, practice question, study guide, test day guide, and test info. Even the three question-providing tools (get_daily_challenge, get_mock_test, get_practice_question) are well-differentiated by format and intent.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case, with most starting with 'get_' (e.g., get_daily_challenge, get_mock_test) and two exceptions (calculate_presence, check_answer) that still adhere to the same verb_noun structure. No mixed conventions.

Tool Count5/5

11 tools is well-scoped for the Canadian citizenship test domain. It covers eligibility calculation, multiple question formats, statistics, guides, and test-day information without being overwhelming or sparse.

Completeness5/5

The tool surface covers the entire lifecycle: eligibility check (calculate_presence), study resources (practice questions, mock tests, study guide, daily challenge), reference info (test info, oath guide, test day guide), statistics, and a question-answer lookup tool. No obvious gaps for the stated purpose.

Resources

Need Help?