Skip to main content
Glama

Georgia Commons

by org.georgiacommons
OverviewDiscussionsAdmin

Read an opinion's text

opinions_get_text
Read-onlyIdempotent

The stored text of an opinion alone, windowed by start and max_chars (default 60,000), with a pointer to continue.

Input Schema

NameRequiredDescriptionDefault
startNoWhere to start, as returned by the previous call's continuation pointer. 0 is the beginning.
opinionYesThe opinion: a docket number (S23A0421), a reporter citation (317 Ga. 528), a record id, or a case name.
max_charsNoMost characters to return in this call, 1,000 to 200,000 (default 60,000). A longer document ends with a pointer to the next part.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / max_chars / description
      Added value: +"Most characters to return in this call, 1,000 to 200,000 (default 60,000). A longer document ends with a pointer to the next part."
    • addedInput schema / properties / max_chars / maximum
      Added value: +200000
    • addedInput schema / properties / max_chars / minimum
      Added value: +1000
    • addedInput schema / properties / opinion / description
      Added value: +"The opinion: a docket number (S23A0421), a reporter citation (317 Ga. 528), a record id, or a case name."
    • addedInput schema / properties / opinion / minLength
      Added value: +1
    • addedInput schema / properties / start / description
      Added value: +"Where to start, as returned by the previous call's continuation pointer. 0 is the beginning."
    • addedInput schema / properties / start / minimum
      Added value: +0
  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 cover read-only, idempotent, non-destructive safety. The description adds that only stored text is returned (no metadata) and that long documents are chunked, but says nothing about behavior when an opinion has no stored text or how the continuation pointer is shaped beyond what the schema states.

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?

One sentence, front-loaded with the resource, then the windowing mechanism and continuation semantics. Nothing wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A single-resource reader with full schema coverage needs little more, but with no output schema the description could have said more about the return shape (text plus continuation pointer field) and about failure/empty cases, which it leaves unstated.

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 100%, so `start`, `opinion`, and `max_chars` are fully documented in the schema already. The description echoes the windowing behavior and default without adding format or edge-case meaning beyond it.

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 verb+resource ('stored text of an opinion') and its scope ('alone', i.e. text without metadata). That scope word is what implicitly separates it from opinions_lookup and opinions_search, though no sibling is named.

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 need to paginate via `start`/continuation is implied, but there is no explicit statement of when to call this versus opinions_lookup or opinions_search, nor any prerequisite guidance.

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