Skip to main content
Glama
Federal Courts Analyst

Federal Courts Analyst

Server info

server_info
Read-onlyIdempotent

Check server version, supported MCP protocol versions, court-statistics database build status, and available tools before querying data.

Instructions

Report this server's version, supported MCP protocol versions, whether its court-statistics database has been built, and which tools it offers.

Call this first if you are unsure whether data is loaded. It takes no arguments, makes no network calls and never changes anything.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "server_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
nameYesHuman-readable server name.
toolsYesNames of the tools this server exposes.
versionYesServer package version (semver).
coverageYesPlain-language summary of what the data covers.
datasetsYesReadiness of each dataset: 'official_tables' (uscourts.gov tables with edition history, courts.duckdb) and 'idb_civil' (FJC Integrated Database civil records, idb.duckdb).
data_statusYes'ready' when the official tables catalog exists; 'not_built' before `make data` has run, in which case data tools will be unavailable. See `datasets` for each dataset.
protocol_versionsYesMCP protocol versions this server can negotiate, newest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already cover read-only, idempotent, non-destructive and closed-world, and the description partly restates that with "never changes anything" and "makes no network calls." It earns credit for adding the failure-mode framing — use it to confirm whether the database has been built before querying — plus the no-arguments cost signal, which the annotations do not convey.

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?

Two short sentences: the first front-loads the full output inventory, the second gives the usage rule and the zero-cost/zero-risk properties. No sentence is 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?

An output schema exists, so return values need not be explained, yet the description still summarizes the payload well enough for an agent to decide whether to call it. For a zero-argument diagnostic tool this is complete.

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?

With zero parameters the baseline is 4, and the description reinforces the schema by stating explicitly that it "takes no arguments," removing any doubt about required input.

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 verb ("Report") and enumerates exactly what is reported: server version, supported MCP protocol versions, database-built status, and available tools. Nothing about it overlaps with data-oriented siblings like find_cases or compare_courts, so an agent can distinguish it immediately.

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

Usage Guidelines4/5

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

It gives an explicit triggering condition: "Call this first if you are unsure whether data is loaded." That is clear when-to-use guidance, though it does not state when the tool is unnecessary or name an alternative diagnostic path.

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