Skip to main content
Glama
Federal Courts Analyst

Federal Courts Analyst

Get an official figure

get_official_figure
Read-onlyIdempotent

Retrieve one official federal court statistic by court and fiscal year, including citation, edition provenance and revision notes. Use for single figures, not rankings or filtered case counts.

Instructions

Use this when the user asks for a single published statistic: one measure, one court (or the nation), one fiscal year, e.g. civil cases pending in S.D.N.Y. in FY2023 or the national median time to disposition.

Not for rankings across courts (use compare_courts), for why a number changed between years (use explain_change), or for counts with filters such as case type (use find_cases).

Returns the value in the latest edition by default, the first-published value, every edition that printed it and, when editions disagree, revision_notes on why. Quote citation with the number, even if asked for one number: it names the edition and any revision. Relay an 'inferred' note as inference. For a 12-month period not ending September 30 (e.g. ending June 30), pass period_ending and relay what the server says. A plain "civil filings" means civil_cases_filed and "civil filings per judgeship" the unweighted civil_filings_per_judgeship (the tables' own labels); pass 'filings_per_judgeship' only for vague asks that name neither.

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

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": "get_official_figure"
  }
}

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
editionNoWhich edition's figure to return: 'latest' (default: the current official figure), 'first_published', or a specific edition such as JB-2020 or JFF-2023.latest
measureYesA published statistic. If the user didn't say whether they mean weighted or unweighted filings, pass 'filings_per_judgeship' (or 'civil_filings') and the server will ask them.
fiscal_yearYesFiscal year (ends September 30).
period_endingNoEnd of the 12-month period: 'september_30' (fiscal year, default) or another quarter end the user asked about.september_30

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.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds substantial behavioral context: it returns the latest edition by default, the first-published value, every printing edition, and revision_notes when editions disagree. It also imposes an obligation to quote the citation and to relay 'inferred' notes as inference, and warns that for a 12-month period not ending September 30 the agent must pass period_ending and relay the server's response — none of which is derivable from annotations.

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 use case, then exclusions, then return behavior, then quirks, then a worked example — a logical order with no filler. A few sentences are dense and run long (the citation and period_ending instructions), but each conveys a distinct operational requirement.

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 five-parameter read tool with an output schema and full annotation coverage, the description covers the remaining agent-facing risks: edition/revision semantics, citation quoting, inference labeling, and non-standard period ends. An agent could call this correctly on the first attempt without consulting anything else.

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%, so the baseline is 3; the description rises above it by mapping natural-language phrasings to specific enum values ('civil filings' → civil_cases_filed, 'civil filings per judgeship' → the unweighted civil_filings_per_judgeship), which the schema does not spell out. Court-code semantics and period_ending are essentially repeated from the schema, limiting it to a 4.

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?

States a precise verb+resource+scope: 'a single published statistic: one measure, one court (or the nation), one fiscal year,' and immediately illustrates with concrete examples (civil cases pending in S.D.N.Y. in FY2023; national median time to disposition). The scope constraint distinguishes it from compare_courts and find_cases without opening either 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?

Explicitly enumerates when NOT to use it and names the correct alternative for each case: rankings across courts → compare_courts, why a number changed → explain_change, counts with filters like case type → find_cases. It also supplies an in-tool routing rule for ambiguous asks (pass filings_per_judgeship and the server asks). Nothing is left to inference.

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