GoThere Citizenship by Descent

Check citizenship by descent eligibility

check_descent_eligibility

Read-onlyIdempotent

Check whether a person qualifies for citizenship by descent.

Input is the person's direct ancestral line, one entry per generation,
starting with relation='self'. Every generation between the person and
the ancestor is required, because descent passes generation by generation
and a gap changes the answer.

Exact dates give the most precise result. Year-only input is accepted and
the result carries a caveat; for Ireland, a registration and a birth in the
same year cannot be resolved.

Args:
    country: ISO 3166-1 alpha-2, lowercase. Currently 'ie' or 'ca'.
    line: The direct line, from the user upward.
    as_of: Evaluation date. Defaults to today. Rules with commencement
        dates (Canada's Bill C-3) depend on it.

Input Schema

Name	Required	Description	Default
`line`	Yes
`as_of`	No
`country`	Yes

Output Schema

Name	Required	Description
`caveats`	No	Approximations and unresolvable ambiguities in the input.
`missing`	No
`sources`	No	Law and official guidance the rules were built from.
`verdict`	Yes	One-line plain reading of the confidence band.
`blockers`	No
`rationale`	Yes
`confidence`	Yes	green, yellow, or red
`disclaimer`	Yes
`learn_more`	Yes
`pathway_id`	Yes
`next_action`	No
`country_code`	Yes
`supporting_facts`	No
`rules_verified_as_of`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 2, 2026

changedInput schema / $defs / LineMember / properties / birth_country / description

Previous value: -"ISO 3166-1 alpha-2 country of birth, e.g. 'IE', 'CA', 'US'. For Northern Ireland use 'IE' — Irish nationality law counts all 32 counties."New value: +"ISO 3166-1 alpha-2 country of birth, e.g. 'IE', 'CA', 'US'. Northern Ireland counts as 'IE': Irish nationality law covers all 32 counties."

changedInput schema / $defs / LineMember / properties / relation / description

Previous value: -"Where this person sits on your direct line. Use exactly one 'self'."New value: +"Where this person sits on the direct line. Exactly one entry is 'self'."

changedOutput schema / properties / caveats / description

Previous value: -"Approximations and unresolvable ambiguities in the input. Relay these."New value: +"Approximations and unresolvable ambiguities in the input."

changedOutput schema / properties / sources / description

Previous value: -"Law and official guidance the rules were built from. Cite these."New value: +"Law and official guidance the rules were built from."

Changed2 schema fields changedNov 2, 2026

addedOutput schema / $defs

Added value: +{
+  "Source": {
+    "properties": {
+      "title": {
+        "title": "Title",
+        "type": "string"
+      },
+      "type": {
+        "description": "'official' or 'secondary'",
+        "title": "Type",
+        "type": "string"
+      },
+      "url": {
+        "title": "Url",
+        "type": "string"
+      }
+    },
+    "required": [
+      "title",
+      "url",
+      "type"
+    ],
+    "title": "Source",
+    "type": "object"
+  }
+}

addedOutput schema / properties / sources

Added value: +{
+  "description": "Law and official guidance the rules were built from. Cite these.",
+  "items": {
+    "$ref": "#/$defs/Source"
+  },
+  "title": "Sources",
+  "type": "array"
+}

First observedOct 13, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds valuable behavioral context beyond annotations: every generation must be supplied, exact dates improve precision, year-only input produces a caveat, and as_of affects commencement-date rules like Canada's Bill C-3.

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 front-loaded with purpose, then immediately explains input shape and date precision caveats. The Args section is focused, with no obvious filler, though the multiple caveat sentences make it slightly longer than strictly necessary.

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

Completeness4/5

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

An output schema exists, so the description need not explain return values. It covers the critical input constraints and evaluation-date behavior well; the main remaining gap is explicit guidance on when this tool is chosen over sibling tools.

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?

Top-level schema description coverage is reported as low, so description compensation matters. The description documents country as lowercase ISO alpha-2 with supported values 'ie' and 'ca', explains that line is ordered from the user upward with relation='self' first, and clarifies that as_of defaults to today and matters for commencement-date rules.

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: checking whether a person qualifies for citizenship by descent. It distinguishes itself from siblings like get_pathway_requirements and list_pathways by focusing on eligibility evaluation for a specific ancestral line.

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?

Usage is implied by the tool's purpose and input requirements, but the description does not explicitly say when to use this tool versus alternatives such as get_pathway_requirements or list_pathways. There are no stated exclusions or routing guidance.

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

All GoThere Citizenship by Descent 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?