OathReady: Canadian Citizenship Test

Get a full mock test

get_mock_test

Read-only

Get a full mock Canadian citizenship test from OathReady's verified bank, in the real exam format (the real test is 20 questions, pass mark 15). Returns questions with answer keys and explanations. Act as quizmaster: present one question at a time, never reveal an answer before the user commits, keep score, and give a pass/fail verdict with 15/20 as the bar.

Input Schema

TableJSON Schema

Name	Required	Description
`count`	No	How many questions (real test is 20)
`topic`	No	Limit to one study topic
`language`	No	Language for the question text (default English; French draws only from translated questions)
`province`	No	Include region-specific questions for this province or territory

Output Schema

TableJSON Schema

Name	Required	Description	Default
`pass_mark`	Yes
`questions`	Yes

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 (default English; French draws only from translated questions)",
+  "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"
+]

First observedJul 21, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses detailed behavioral expectations: it returns questions with answer keys and explanations, and instructs the agent to act as quizmaster by presenting one question at a time, withholding answers until the user commits, keeping score, and applying the 15/20 pass bar. This is rich, actionable context beyond what annotations provide.

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?

The description is compact and front-loaded: the first sentence states the core purpose, the second notes the return contents, and the third gives clear operating instructions. Every sentence earns its place with no redundancy.

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 tool's simplicity, 4 optional parameters with full schema coverage, and an existing output schema, the description provides everything needed: what the tool returns, the exam format, the passing threshold, and how the agent should conduct the quiz. Nothing critical is missing for correct invocation and use.

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%, so the baseline is 3. The description adds one parameter-related fact ('real test is 20 questions, pass mark 15') that reinforces the count default, but it does not add meaningful semantics for topic, language, or province beyond what the schema already describes.

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 states a specific verb and resource: 'Get a full mock Canadian citizenship test' from a verified bank in real exam format. It clearly differentiates from siblings like get_practice_question by emphasizing 'full mock test' and 'real exam format.'

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?

The description gives clear context that this is for full mock tests in exam format, but does not explicitly name alternatives or state when not to use it. The usage is implied rather than directly stated, so it does not fully satisfy the when-to-use vs alternatives criterion.

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?