KnowJudges

get_immigration_analytics

Read-only

Get immigration judge or court outcomes using its canonical public profile URL. Filter jointly by nationality, calendar/fiscal proceeding-completion year and recorded court state. Asylum grant/denial percentages use grant-coded plus denied outcomes; procedural outcomes are separate. Samples below 35 decisions are labeled; no decisions means no rate. Returns sources and coverage. Use proceeding_removal_rate only for explicitly requested broader proceeding outcomes.

Input Schema

TableJSON Schema

Name	Required	Default
`year`	No
`state`	No
`entity`	Yes
`metric`	No	asylum_denial_rate
`year_basis`	No	calendar
`nationality`	No
`profile_url`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`state`	Yes
`metric`	Yes
`period`	Yes
`source`	Yes
`message`	Yes
`results`	Yes
`limitations`	Yes
`nationality`	Yes
`availability`	Yes
`eligible_entities`	Yes
`minimum_decisions`	Yes
`geography_definition`	Yes
`denominator_definition`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 12, 2026

removedInput schema / properties / state / pattern
```
Removed value: -"^[A-Za-z]{2}$"
```

addedOutput schema / properties / results / items / properties / outcome_denominator

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / results / items / properties / relief_granted

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / results / items / properties / removal_orders

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed3 schema fields changedOct 10, 2026

addedOutput schema / properties / results / items / properties / grant_rate

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 100,
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / results / items / properties / sample_note

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / results / items / required

Previous value: -[
-  "name",
-  "profile_url",
-  "court_name",
-  "court_url",
-  "granted",
-  "denied",
-  "other_outcomes",
-  "excluded",
-  "decisions",
-  "denial_rate",
-  "removal_rate",
-  "current_roster_count",
-  "analytics_judge_count"
-]New value: +[
+  "name",
+  "profile_url",
+  "court_name",
+  "court_url",
+  "granted",
+  "denied",
+  "other_outcomes",
+  "excluded",
+  "decisions",
+  "grant_rate",
+  "denial_rate",
+  "removal_rate",
+  "sample_note",
+  "current_roster_count",
+  "analytics_judge_count"
+]

AddedOct 9, 2026

TDQS

A4.1/5.0

Behavior5/5

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

With annotations already declaring readOnlyHint, destructiveHint, and openWorldHint, the description adds valuable behavioral context beyond them: how asylum grant/denial percentages are computed, that procedural outcomes are separate, that samples below 35 decisions are labeled, that no decisions means no rate, and that sources and coverage are returned.

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 front-loaded with the core purpose, then layers necessary filter and metric semantics without filler. Despite its length, every sentence contributes information useful to correct invocation or interpretation.

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 return values need not be fully described, though the description still helpfully notes sources and coverage. It covers the unusual analytical rules and sample thresholds needed to interpret results correctly, but could say more about how an agent should obtain or validate the required canonical profile_url.

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?

Schema description coverage is 0%, so the description must carry the burden. It maps most parameters to meaning: entity as judge/court, profile_url as canonical public profile, nationality, calendar/fiscal year, court state, and the metric choice including the proceeding_removal_rate caveat. It does not cover year bounds, nationality length limits, or the default metric value, so it is not fully exhaustive.

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 states a specific verb and resource: getting immigration judge or court outcomes via a canonical profile URL. It does not name the closely related sibling compare_immigration_analytics or explain how this differs from profile-oriented tools, so it is clear but not sibling-differentiating.

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 some usage direction: filter jointly by nationality, calendar/fiscal proceeding-completion year, and court state, and use proceeding_removal_rate only for explicitly requested broader outcomes. However, it never says when to choose this tool over compare_immigration_analytics or the profile-fetching siblings, leaving tool selection implied.

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

All KnowJudges 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.