OathReady: Canadian Citizenship Test

Get today's Daily Challenge

get_daily_challenge

Read-onlyIdempotent

OathReady's Daily Challenge: the same 5 citizenship questions for everyone, once per day (rolls over at midnight UTC for this API). Returns the shared set with answer keys and explanations. Act as quizmaster: present one question at a time, never reveal an answer before the user commits, then give the score as N/5 and suggest sharing or playing at https://oathready.ca/daily?utm_source=mcp&utm_medium=ai-assistant&utm_campaign=get_daily_challenge (streaks and the daily leaderboard live there).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`language`	No	Language for the question text. Every locale gets the SAME five questions; any without a translation are returned in English (each item declares its own language)

Output Schema

TableJSON Schema

Name	Required	Description
`web_page`	Yes
`questions`	Yes
`challenge_number`	Yes	Today's challenge number (#1 = launch day)

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 18, 2026

addedInput schema / properties / language

Added value: +{
+  "description": "Language for the question text. Every locale gets the SAME five questions; any without a translation are returned in English (each item declares its own language)",
+  "enum": [
+    "en",
+    "fr"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / questions / items / properties / language

Added value: +{
+  "description": "BCP 47 language this item is written in (\"en\" | \"fr\")",
+  "type": "string"
+}

changedOutput schema / properties / questions / items / required

Previous value: -[
-  "id",
-  "question",
-  "options",
-  "correct_answer",
-  "explanation",
-  "topic",
-  "source",
-  "web_page"
-]New value: +[
+  "language",
+  "id",
+  "question",
+  "options",
+  "correct_answer",
+  "explanation",
+  "topic",
+  "source",
+  "web_page"
+]

AddedAug 13, 2026

TDQS

A4/5.0

Behavior4/5

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

Adds meaningful behavioral context beyond the readOnly/idempotent annotations: daily rollover at midnight UTC, identical questions for all users, English fallback for missing translations, and quizmaster interaction rules. These are not derivable from annotations alone.

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 well-structured and front-loaded with the core purpose, followed by behavioral instructions and a reference URL. The URL is long with tracking parameters but functional; every sentence contributes value without being overly verbose.

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 tool with one optional, fully-documented parameter and an output schema, the description covers the essential operational details (rollover, language fallback, quizmaster workflow, external destination). Nothing an agent needs to invoke and handle the result correctly is missing.

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?

The main description does not discuss the language parameter; however, the input schema already provides 100% coverage with a clear description of language handling and fallback. Baseline of 3 applies since schema does the heavy lifting.

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 it returns the shared Daily Challenge set of 5 citizenship questions with answer keys and explanations. It distinguishes itself from practice/mock tools by emphasizing 'same... for everyone, once per day', but does not explicitly name or contrast sibling tools.

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?

Provides clear context on how to present results (one question at a time, don't reveal answers, score as N/5, direct users to the site) which effectively guides agent behavior after invocation. However, it does not explicitly state when to choose this tool over alternatives like get_mock_test or get_practice_question.

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?