Skip to main content
Glama

Pa Code Section

pa_code_section
Read-onlyIdempotent

Get the FULL TEXT of a section of the Pennsylvania Code (the state's administrative REGULATIONS, not the Consolidated Statutes) by citation, e.g. "25 Pa. Code § 105.13" or "55 Pa. Code § 3270.1". Returns the current text with subsection structure, the Authority and Source notes, and the date through which the Code is current. Pass citation ("25 Pa. Code § 105.13") or title + section. Optional subsection (e.g. "d") returns just that subsection. Keyless.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "citation": "25 Pa. Code § 105.13"
    },
    "name": "pa_code_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoPennsylvania Code title number, e.g. "25" (Environmental Protection), "55" (Human Services), "52" (Public Utilities).
sectionNoSection number as cited, e.g. "105.13" or "3270.1". The part before the dot is the chapter.
citationNoFull citation, e.g. "25 Pa. Code § 105.13" or "55 Pa. Code 3270.1". Alternative to title + section.
subsectionNoOptional lettered subsection to return alone, e.g. "d" or "(d)".

Output Schema

NameRequiredDescriptionDefault
urlNo
textNo
foundNo
titleNo
reasonNo
sourceNo
headingNo
messageNo
sectionNo
citationNo
authorityNo
data_as_ofNo
subsectionNo
text_charsNo
source_noteNo
subsectionsNo
current_throughNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description does add real value beyond that: "Keyless" discloses that no auth is needed, and it discloses what comes back (subsection structure, Authority/Source notes, currency date). It omits failure behavior (what happens on a bad or nonexistent citation).

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?

Purpose and the regulation/statute distinction are front-loaded in the first clause, then addressing modes, then the optional narrowing, then the keyless note. Every sentence carries a distinct fact; nothing is repeated from the schema.

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?

Output schema exists, yet the description still summarizes the return shape (full text, subsections, Authority/Source, currency date) at the right altitude. Auth model, addressing modes, narrowing option, and corpus boundary are all covered for a 4-parameter retrieval tool.

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 coverage is 100%, so baseline is 3; the description adds meaning on top by framing `citation` vs `title`+`section` as mutually alternative addressing modes (a relationship the flat schema does not express) and by clarifying that `subsection` returns just that subsection rather than the whole section.

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?

Uses a specific verb+resource ("Get the FULL TEXT of a section of the Pennsylvania Code") and immediately disambiguates the corpus from the Consolidated Statutes, which is the exact confusion an agent would have. The example citations make the target unambiguous.

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?

Explicitly states the two acceptable addressing modes (full `citation`, or `title` + `section`) and that `subsection` is optional narrowing to a single subsection. It carves out the statute-vs-regulation boundary, though it does not name `pa_code_search` as the alternative for when you lack a precise citation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.