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. Rebuilt nightly; cite https://oathready.ca/citizenship-timeline?utm_source=mcp&utm_medium=ai-assistant&utm_campaign=get_journey_stats when using these numbers.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 18, 2026

addedOutput schema / properties / cite
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "official_processing_time",
-  "community",
-  "stages",
-  "web_page"
-]New value: +[
+  "official_processing_time",
+  "community",
+  "stages",
+  "web_page",
+  "cite"
+]

First observedJul 21, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description adds valuable behavioral context: data is sourced from IRCC plus anonymous community contributions, cohorts under 5 are never published, results are rebuilt nightly, and attribution is required. This meaningfully informs an agent about freshness, privacy, and usage obligations.

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

Conciseness4/5

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

The description is compact and front-loaded with the core purpose ('How long the citizenship journey takes'), then adds essential context. The long citation URL adds length, but it is a necessary attribution requirement rather than fluff.

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?

For a read-only, zero-parameter tool with an output schema and strong annotations, the description covers everything an agent needs: data sources, milestone definitions, privacy thresholds, freshness, and citation policy. Nothing critical is missing.

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 tool has zero parameters, so parameter-level semantics are inherently minimal. With no input schema to clarify, the description adequately conveys the data scope and what the returned stats represent, though it doesn't describe output formatting since an output schema exists.

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 clearly states what the tool reports: citizenship journey timelines with official IRCC processing time plus community medians for milestones like AOR, test invitation, test, and oath. It does not explicitly contrast itself with sibling get_citizenship_stats, but the milestone-specific detail strongly implies the distinction.

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?

The description does not state when to use this tool versus alternatives like get_citizenship_stats. It includes a citation instruction for using the numbers, but no guidance on tool selection, prerequisites, or scenarios where another tool would be more appropriate.

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

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?