Skip to main content
Glama
Federal Courts Analyst

Federal Courts Analyst

Judgeship context

judgeship_context
Read-onlyIdempotent

Compare a district court's weighted filings per judgeship against Judicial Conference 430/600 thresholds, with its 2025 judgeship recommendation and neutral context.

Instructions

Use this when the user asks how a district's workload compares with the Judicial Conference's standards for new judgeships, or whether the Conference recommended judgeships for it: "Is E.D. Tex. above the 430 threshold?", "judgeship context for E.D.N.C.".

Not for rankings (compare_courts) or for the raw figure alone (get_official_figure).

Returns the court's official weighted filings per judgeship (Table X-1A), weighted civil filings and authorized judgeships from the same edition, the national figure, the 430 and 600 thresholds with their sources, the Conference's 2025 recommendation for the court if any, and a neutral summary. The server never recommends judgeships itself and can't say whether a court has a judicial emergency (that needs vacancy data): don't imply either. Asked whether a court should get judgeships, give these facts and the Conference's recommendation, say it's a decision for Congress, and don't argue either side.

Example: court='TX-E', fiscal_year=2025 → 894 weighted filings per judgeship (JB-2025), above 430 and 600; the Conference recommended 2 more judgeships.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "court": "<court>"
    },
    "name": "judgeship_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
courtYesCourt code: US (all district courts), a circuit (CIR-01 … CIR-11, CIR-DC) or a district (state postal code, plus -N/-E/-S/-W/-M/-C for divided states: FL-N = N.D. Fla., NY-S = S.D.N.Y., DC = D.D.C.).
fiscal_yearNoDefault: latest.

Output Schema

NameRequiredDescriptionDefault
dataNo
statusNook
declinedNo
warningsNo
provenanceNo
clarificationNo
suggested_nextNoHints for a follow-up call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already establish the safety profile (readOnly, idempotent, non-destructive, closed-world) and an output schema exists, so those need no restatement. The description does add genuinely behavioral material beyond that: the server's own limits (it never recommends judgeships and cannot speak to judicial emergencies because it lacks vacancy data) and a prescribed response posture when asked whether a court should get judgeships. That guardrail content is valuable and non-obvious.

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?

Well front-loaded: trigger, exclusions, returns, guardrails, example in that order. The two guardrail sentences overlap somewhat — one states what the server cannot do, the other how to answer a recommendation question — and could be tightened, but each carries distinct instructions rather than filler.

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 policy-sensitive lookup with only two parameters and a rich output schema, this covers everything an agent needs: what data comes back (Table X-1A figures, thresholds with sources, the 2025 recommendation, a neutral summary), the edition-consistency caveat, and the framing constraints that keep the response from overstating what the data supports.

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 coverage is 100% and the court enum plus fiscal_year default are fully documented in the schema, so the baseline would be 3. The description exceeds that by tying inputs to a worked example (court='TX-E', fiscal_year=2025 → 894 weighted filings per judgeship, above both thresholds, Conference recommended 2 more), which shows what a fiscal_year pin actually changes and what a court code resolves to.

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 names a specific analytical resource — a court's workload versus the Judicial Conference's judgeship standards and the Conference's actual recommendation — and immediately distinguishes it from the two nearest siblings (compare_courts for rankings, get_official_figure for the raw number). Two concrete user phrasings ('Is E.D. Tex. above the 430 threshold?') anchor the purpose in recognizable intent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives both sides explicitly: a 'use this when' trigger with example utterances, plus a 'not for' line naming the alternatives and the condition that routes to each. An agent can pick between judgeship_context, compare_courts, and get_official_figure without opening any schema.

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