Skip to main content
Glama
Sign In

Georgia Code

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ga Code Search

ga_code_search
Read-onlyIdempotent

Search the Official Code of Georgia Annotated BY TOPIC or keyword rather than citation — "security deposit", "concealed carry", "DUI per se limit", "homicide". Full-text search over the statutory text and catchlines; returns ranked sections with their citations and a highlighted snippet so you can call ga_code_section for the full text of one. Pass "headings_only": true to match only chapter/article headings and catchlines rather than body text. 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": {
      "limit": 5,
      "query": "security deposit return"
    },
    "name": "ga_code_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 10, max 25.
queryYesTopic or keywords, e.g. "security deposit return".
headings_onlyNoMatch only headings/catchlines, not body text. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, open-world behavior, and the description adds substantial value beyond them: return format (ranked sections with citations and a highlighted snippet), the effect of headings_only on matching scope, and that the tool is keyless.

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?

Front-loads the core action and the topic-vs-citation distinction, then gives illustrative queries, then the routing hint. Every sentence carries information; no filler.

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?

No output schema exists, yet the description explains the return shape well enough for an agent to consume results (ranked sections, citations, snippet). Auth (keyless), scope, and the follow-up tool are all covered.

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 100%, so the schema already documents limit, query, and headings_only. The description reinforces query semantics with natural-language examples ("security deposit", "DUI per se limit") but adds little syntax or format detail beyond the schema, so baseline 3 applies.

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?

Specific verb (Search) plus a precisely named resource (Official Code of Georgia Annotated), scoped to topic/keyword rather than citation. It is clearly distinguishable from the sibling ga_code_section, which it explicitly routes to for full text.

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 states when to use it ('BY TOPIC or keyword rather than citation') and names the alternative for retrieving full text (ga_code_section). The headings_only option is tied to a concrete use case (match only headings/catchlines rather than body text).

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

All Georgia Code toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources