Georgia Prisoners' Speak Public Data

Get page

get_page

Read-onlyIdempotent

Read any gps.press page as clean Markdown.

Every page on the site has a Markdown twin at the same URL with `.md` appended;
this fetches it. Accepts a full URL, a path, or a bare slug — '/vision2027/',
'vision2027', and the full https URL all work, with or without '.md'.

Covers articles, data pages, campaign pages and the intelligence briefings
(intelligence/facility/{slug}, intelligence/issue/{slug}).

Long pages are truncated; use `offset` and `limit` to page through one. Pair with
search_site() to find a page, then read it here rather than guessing its contents.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	Yes
`limit`	No
`offset`	No

Schema Changelog

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

First observedSep 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already indicate read-only and idempotent behavior. The description adds valuable behavioral details beyond that: it fetches the .md twin, accepts URL/path/slug forms, truncates long pages, and supports offset/limit pagination.

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 four focused sentences with the core purpose front-loaded. Every sentence adds value: accepted inputs, page coverage, truncation behavior, and a sensible pairing workflow.

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 simple read tool with no output schema, the description covers return format, accepted inputs, page scope, and pagination. An agent has enough context to select and call it correctly, including knowing to search before fetching.

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?

Schema description coverage is 0%, so the description carries the burden and it largely succeeds. It fully explains the path parameter's accepted input forms and explains how offset and limit are used for pagination, though it does not define bounds or special values.

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 the exact verb 'Read' and the resource 'gps.press page as clean Markdown', then enumerates the page types it covers. This clearly differentiates it from sibling tools that fetch specific datasets.

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 provides an explicit workflow: pair with search_site() to find a page, then read it here rather than guessing contents. It does not spell out when not to use this tool versus other sibling fetchers, but the context is clear.

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?