Georgia Prisoners' Speak Public Data

Get gps guide

get_gps_guide

Read-onlyIdempotent

GPS's orientation file for AI clients (llms.txt) — READ THIS FIRST.

Carries the things the data tools cannot: which figure to lead with when two are
defensible, how to label budget figures, the exact date of the DOJ findings report,
and the claims GPS has publicly corrected and will not repeat. Roughly 2,000 words.

The datasets give you accurate numbers. This is what keeps the sentence around the
number accurate too.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

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

First observedSep 6, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already mark this as read-only, idempotent, and non-destructive. The description adds meaningful context beyond that: it is roughly 2,000 words, contains editorial guidance, and includes claims GPS has publicly corrected and will not repeat. This clarifies expected behavior and content without contradicting the 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?

The description is compact and front-loaded with the most important instruction, READ THIS FIRST. It efficiently lists the types of guidance contained in the file. The final metaphorical sentence earns its place by clarifying the tool's complementary role to the data tools.

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 zero-parameter, read-only tool with no output schema, the description is complete enough. It tells the agent what the file is, why it matters, roughly how long it is, what guidance it contains, and where it fits relative to sibling data tools.

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?

The tool has zero parameters, so the schema fully covers parameter expectations and the description has no parameter burden. The baseline of 4 applies because there is nothing for the description to clarify.

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 clearly identifies the tool as retrieving GPS's orientation file for AI clients, specifically the llms.txt file, and states READ THIS FIRST. It distinguishes itself from sibling data tools by explaining it carries interpretative guidance rather than raw dataset numbers.

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?

The description gives an explicit directive to use this tool first, and explains that it carries context the data tools cannot, such as which figures to lead with and which claims to avoid. The final paragraph reinforces the division of labor: datasets provide accurate numbers; this tool keeps the surrounding wording accurate.

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?