Skip to main content
Glama

Georgia Commons

by org.georgiacommons
OverviewDiscussionsAdmin

List Supreme Court of Georgia opinions by year

opinions_list
Read-onlyIdempotent

The opinions filed in a year (the newest year when omitted), in filing order, 25 a page: docket, date, case name, case type, URL. Filter by case_type (criminal appeal, civil, bar discipline, habeas, certified question, election, other) or words q.

Input Schema

NameRequiredDescriptionDefault
qNoWords every listed opinion must contain.
yearNoThe year filed (opinions are held from 2020 on). Omit for the newest year.
limitNoHow many entries per page, 1 to 40 (default 25).
startNoHow many entries to skip, as returned by the previous call's continuation pointer. 0 is the first page.
case_typeNoKind of case: criminal appeal, civil, bar discipline, habeas, certified question, election, or other.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedInput schema / properties / case_type / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "criminal appeal",
+      "civil",
+      "bar discipline",
+      "habeas",
+      "certified question",
+      "election",
+      "other"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / case_type / description
      Added value: +"Kind of case: criminal appeal, civil, bar discipline, habeas, certified question, election, or other."
    • addedInput schema / properties / limit / description
      Added value: +"How many entries per page, 1 to 40 (default 25)."
    • addedInput schema / properties / limit / maximum
      Added value: +40
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / q / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 500,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / q / description
      Added value: +"Words every listed opinion must contain."
    • addedInput schema / properties / start / description
      Added value: +"How many entries to skip, as returned by the previous call's continuation pointer. 0 is the first page."
    • addedInput schema / properties / start / minimum
      Added value: +0
    • changedInput schema / properties / year / anyOf
      Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 2100,
+    "minimum": 2000,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / year / description
      Added value: +"The year filed (opinions are held from 2020 on). Omit for the newest year."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value by disclosing filing order, page size, and the exact returned fields (important since there is no output schema), but it omits how filters interact with pagination or whether start must reset when the year changes.

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?

A single dense sentence that front-loads the result shape and follows with pagination and filters; every clause carries information, notably the returned field list. Slightly compressed phrasing ('25 a page', backticked field names) keeps it tight without waste.

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?

With five optional parameters and no output schema, the description usefully supplies the return fields and paging model, which is the main risk area. The remaining gap is filter/pagination interaction and the absence of routing guidance to sibling search tools.

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 description coverage is 100%, so all five parameters are already documented, including the case_type enum members and the year range. The description restates the enum values and 'words q' without adding constraints or interaction semantics beyond the schema, so baseline 3 applies.

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?

States a specific resource (Supreme Court of Georgia opinions) and a specific scope (filed in a year, in filing order, paginated). It distinguishes itself implicitly from opinions_search by emphasizing year-based listing, but never names the sibling or clarifies the overlap with keyword search, so it falls short of a 5.

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 parenthetical '(the newest year when omitted)' gives a default-behavior cue and 'Filter by case_type ... or words q' hints at filtering usage. However, it never says when to use this list operation instead of opinions_search or opinions_lookup, which are the obvious alternatives for keyword retrieval.

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

All Georgia Commons toolsInspect
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.

Resources