Skip to main content
Glama

Pa Code Search

pa_code_search
Read-onlyIdempotent

Full-text search of the Pennsylvania Code (state administrative regulations). Returns matching sections with citation, heading and a snippet. Use for "which Pennsylvania regulation covers X". Optional title restricts to one Code title (e.g. "25"). Pennsylvania Code regulations only; for statutes use pa_consolidated_statute. 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": {
      "query": "dam safety permit fees",
      "title": "25"
    },
    "name": "pa_code_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page, 1-based (10 results per page). Default 1.
queryYesWords or "quoted phrase" to find, e.g. "dam safety permit fees".
titleNoOptional Pennsylvania Code title number to restrict to, e.g. "25" or "55".

Output Schema

NameRequiredDescriptionDefault
countNo
foundNo
queryNo
titleNo
reasonNo
sourceNo
messageNo
resultsNo
data_as_ofNo
total_resultsNo
current_throughNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive) and open-world behavior, and the description contributes beyond them: the return shape (citation, heading, snippet) and that the tool is keyless, removing auth concerns. Remaining gaps, such as result volume, pagination, and relevance ranking, are left to the schema or output schema.

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?

Front-loaded with the resource and purpose, then the scope restriction, then the sibling redirect, then the keyless note. Every sentence carries signal, though the closing "Keyless." is a fragment that reads as an afterthought rather than integrated context.

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

Completeness4/5

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

An output schema exists and annotations cover the safety profile, so the description does not need to explain return values, but it helpfully does so in one clause. It is complete enough to call correctly, with only minor omissions such as page size and result-count expectations.

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 the schema already documents query, title, and page. The description only repeats the title restriction and its example values ("25"), adding no syntax or edge-case meaning beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource ("Full-text search of the Pennsylvania Code") plus what it returns ("matching sections with citation, heading and a snippet"). It also explicitly distinguishes itself from pa_consolidated_statute, so an agent can route between them without opening either schema.

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?

Names the concrete question it answers ("which Pennsylvania regulation covers X") and gives an explicit exclusion with the alternative to use instead ("Pennsylvania Code regulations only; for statutes use pa_consolidated_statute"). Nothing about when to pick it over a sibling is left to inference.

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.