Skip to main content
Glama

Georgia Commons

by org.georgiacommons
OverviewDiscussionsAdmin

code_search

Read-onlyIdempotent

Full-text search of the Code: words, or a citation, or both. A citation among words returns that section first; a query that names an act returns the section stating its short title first; a query that is a passage of a provision word for word returns that provision first. Search matches the words of the document: ask in the words the statute would use. in_headings searches only headings and catchlines and adds the matching units. scheme picks the collection: ocga (default), ga for the Georgia constitution, us for the United States constitution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes
titleNo
schemeNoocga
chapterNo
in_headingsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / scheme
      Added value: +{
+  "default": "ocga",
+  "title": "Scheme",
+  "type": "string"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds genuine behavioral value by explaining result-ranking rules (citations, act names, verbatim passages surface first) and collection scoping via scheme.

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-loads purpose, then ranking behavior, then parameter notes. Dense but every clause earns its place; no filler sentences.

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

Completeness3/5

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

No output schema exists so return values needn't be explained, and search semantics are well covered. However, with 4 of 6 parameters (title, chapter, limit) unexplained and no sibling routing, the definition is incomplete for a tool sitting among several closely related code-lookup tools.

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 0%, so the description carries the full parameter burden, and it explains only 2 of 6 params — in_headings and scheme (with its values and default). The title, chapter, limit, and query parameters are left undocumented, so it only partially compensates for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 Code") and details what can be searched (words, citation, or both). It stops short of explicitly differentiating itself from siblings like code_lookup_section or code_find_act, so it doesn't reach a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Offers real query-formulation guidance ("ask in the words the statute would use") and describes how citation-naming and verbatim-passage queries behave, but never states when to use this tool versus the many sibling lookup/search tools. Usage is implied rather than prescribed.

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

All Georgia Commons 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