Skip to main content
Glama
Federal Courts Analyst

Federal Courts Analyst

Can this go to the statistics office?

check_inquiry_eligibility
Read-onlyIdempotent

Determine whether a federal court statistic was revised between editions without a published explanation, so you know if it is eligible for an inquiry to the statistics office.

Instructions

Use this before offering "Ask the statistics office why this changed": it says whether a figure was revised between editions with no published explanation, which is the only kind of question the office gets.

Not for the figure itself or its edition history (use get_official_figure), or for filing the question (use keep_answer with option 'ask_office').

Returns eligible true or false, why, and the revision (first and latest edition and value). Read-only.

Example: measure='weighted_civil_filings_per_judgeship', court='US', fiscal_year=2020 → eligible: 554 (JB-2020) → 322 (JFF-2025), no published explanation.

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": {
      "measure": "<measure>",
      "fiscal_year": "<fiscal_year>"
    },
    "name": "check_inquiry_eligibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
courtNoCourt 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.).US
measureYesA published statistic (see courts://glossary or explain_term for definitions).
fiscal_yearYes

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.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the trailing 'Read-only.' adds nothing and earns no credit. What the description does add is the admissibility rule behind the boolean (revised between editions, no published explanation) and the shape of the verdict, but with an output schema present even the return detail is largely redundant.

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?

Front-loaded with the trigger, then exclusions, then return, then a compact example — a sensible order with little waste. The clause 'which is the only kind of question the office gets' is slightly convoluted and 'Read-only.' is dead weight given the annotations.

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?

For a three-parameter gate tool with an output schema and full annotations, this covers the trigger, the exclusions, and the decision rule. The remaining gap is fiscal_year semantics — which editions a year maps to — left to the output rather than explained.

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 coverage is 67%: court and measure carry enum descriptions, while fiscal_year is bare apart from min/max. The worked example shows how the three parameters combine and implicitly ties fiscal_year to an edition (JB-2020 to JFF-2025), which is a small but real addition beyond the schema; it does not, however, explain the fiscal-year-to-edition mapping.

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 concrete decision: whether a figure was revised between editions with no published explanation, i.e. whether an inquiry to the statistics office is admissible. It distinguishes itself explicitly from get_official_figure (the figure/edition history) and from keep_answer (filing the question), so an agent can route correctly without opening any schema.

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 an explicit trigger ('Use this before offering "Ask the statistics office why this changed"') plus two named exclusions with the sibling and argument to use instead. Both the when and the when-not are spelled out.

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