Georgia Prisoners' Speak Public Data

Search quotes

search_quotes

Read-onlyIdempotent

Search GPS's published quote collection — statements from incarcerated people, families, officials and staff that GPS has already published.

`attribution_type` is 'named' or 'anonymous'. `category` is one of the
published categories (call with no arguments and read the results, or see
gps.press). Paginated: page starts at 1, per_page caps at 100.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No
`search`	No
`category`	No
`per_page`	No
`attribution_type`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds useful behavioral details beyond the annotations: attribution_type accepts 'named' or 'anonymous', categories are discoverable via an empty call, and pagination starts at page 1 with per_page capped at 100. This is concrete and non-redundant.

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?

The description is compact and well-structured: scope first, then parameter semantics, then pagination. Every sentence adds useful information with no filler or repetition.

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?

The tool has no output schema and five parameters, and while category discovery and pagination are addressed, the 'search' parameter's behavior and the result format are left unspecified. Still, the description provides enough to make a safe first call and explore the collection.

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 0%, so the description must compensate for the schema's lack of parameter documentation. It explains attribution_type, category discovery, and page/per_page bounds, but it leaves the 'search' parameter semantically undefined—what it matches and how it behaves is not stated.

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?

Description states a specific verb and resource: 'Search GPS's published quote collection', and clarifies the content scope as statements from incarcerated people, families, officials and staff that GPS has already published. This clearly distinguishes it from sibling data-retrieval tools and search_site.

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 description conveys the intended use case—searching already-published quotes—and gives helpful operational guidance such as calling with no arguments to discover categories. However, it does not explicitly contrast this tool with search_site or other siblings, so when-not-to-use is implied rather than stated.

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

All Georgia Prisoners' Speak Public Data tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool names a distinct resource or action: contraband incidents vs summaries, a single facility vs facility list vs staff roster, and site-wide search vs quote search. The few close pairs are complementary rather than duplicative, and descriptions explicitly indicate when to use each.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (get_*, list_*, search_*). The one outlier, get_gps_guide, still fits the get_<resource> convention, so there is no real style clash.

Tool Count4/5

At 18 tools the server is heavier than a minimal CRUD surface, but it covers a broad public-data domain with a distinct endpoint per dataset or site function. The count feels slightly over the typical sweet spot rather than bloated or redundant.

Completeness4/5

The major GPS data domains are represented: facilities, population, mortality, contraband, parole, length of stay, settlements, and legal text. A few potentially relevant datasets (e.g., a structured budget tool) are not exposed directly, but search_site plus get_page cover most of those gaps.

Resources

Need Help?