OathReady: Canadian Citizenship Test

Get a practice question

get_practice_question

Read-only

Get one random Canadian citizenship test practice question from OathReady's verified bank (based on the official Discover Canada guide). Returns the question, shuffled options, the correct answer, and an explanation. Act as quizmaster: show the user ONLY the question and options, wait for their pick, then grade it and share the explanation.

Input Schema

TableJSON Schema

Name	Required	Description
`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
`id`	Yes	Stable question id, e.g. q-042
`topic`	Yes
`source`	Yes
`options`	Yes	Answer choices in display order
`language`	Yes	BCP 47 language this item is written in ("en" \| "fr")
`question`	Yes
`web_page`	Yes	This question's page on oathready.ca
`explanation`	Yes
`correct_answer`	Yes	Do not reveal until the user has answered

TDQS

A4.5/5.0

Behavior5/5

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

The description fully discloses the interactive behavior beyond the readOnlyHint annotation. It explains the expected flow (show, wait, grade, explain) and confirms the read-only nature. No contradictions with annotations.

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?

Three sentences: purpose, return content, and usage instruction. No fluff, front-loaded with the core action. Every sentence earns its place.

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?

The description covers the tool's purpose, return structure, and interactive usage. With an output schema present, the description is sufficient for an agent to understand the tool and use it correctly. All optional parameters are explained in the schema.

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 schema covers all three parameters with descriptions (topic, language, province). The tool description adds context about the source (OathReady's verified bank) and the quizmaster flow, but does not enhance parameter meaning beyond what the schema already provides. With 100% schema coverage, baseline 3 is appropriate.

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 states the tool retrieves one random practice question from a verified bank, and specifies the quizmaster interaction pattern. It is distinct from siblings like get_mock_test or get_daily_challenge by focusing on a single question with an interactive flow.

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 gives explicit instructions on how to use the tool: show only question and options, wait for user pick, then grade and explain. This is a clear usage guideline. It does not explicitly compare to alternatives, but the context of sibling tools and the 'random' nature imply it is for isolated practice, not full tests.

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?