Skip to main content
Glama

Georgia Commons

by org.georgiacommons
OverviewDiscussionsAdmin

Look up a Georgia General Assembly bill

bills_lookup
Read-onlyIdempotent

One bill or resolution of the Georgia General Assembly by number in any written form (HB 136, H.B. 136, House Bill 136, 2025-2026/hb136, a numeric id), as the same Markdown twin the site serves: frontmatter (cite_as, canonical_url, source_url, status), the verbatim text, the summaries Georgia Commons wrote under a heading that says so, and status. With no session, a number means the newest regular session that has it; name the session (2026-special) for a special session's bill that shares its number. full adds the history, the floor votes with how each member voted, the amendments, and every document the legislature lists. Returns at most max_chars characters (default 60,000); a longer bill ends with the call for the next part.

Input Schema

NameRequiredDescriptionDefault
billYesThe bill or resolution: HB 136, H.B. 136, House Bill 136, SR 5, 2025-2026/hb136, or a numeric id.
fullNoInclude the optional material the tool describes (for example votes and history, or the notes). Longer.
startNoWhere to start, as returned by the previous call's continuation pointer. 0 is the beginning.
sessionNoThe session, named by its years or slug: 2025-2026 (the regular session) or 2026-special. Omit for the default the tool describes.
max_charsNoMost characters to return in this call, 1,000 to 200,000 (default 60,000). A longer document ends with a pointer to the next part.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / bill / description
      Added value: +"The bill or resolution: HB 136, H.B. 136, House Bill 136, SR 5, 2025-2026/hb136, or a numeric id."
    • addedInput schema / properties / bill / minLength
      Added value: +1
    • addedInput schema / properties / full / description
      Added value: +"Include the optional material the tool describes (for example votes and history, or the notes). Longer."
    • addedInput schema / properties / max_chars
      Added value: +{
+  "default": 60000,
+  "description": "Most characters to return in this call, 1,000 to 200,000 (default 60,000). A longer document ends with a pointer to the next part.",
+  "maximum": 200000,
+  "minimum": 1000,
+  "title": "Max Chars",
+  "type": "integer"
+}
    • addedInput schema / properties / session / description
      Added value: +"The session, named by its years or slug: 2025-2026 (the regular session) or 2026-special. Omit for the default the tool describes."
    • addedInput schema / properties / start
      Added value: +{
+  "default": 0,
+  "description": "Where to start, as returned by the previous call's continuation pointer. 0 is the beginning.",
+  "minimum": 0,
+  "title": "Start",
+  "type": "integer"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations establish a safe, read-only, idempotent lookup, and the description adds substantial behavioral detail: the Markdown twin format, frontmatter fields, verbatim text, summaries, status, expanded full content, and truncation with a continuation pointer. This is rich context beyond the structured annotations.

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?

The purpose is front-loaded and every sentence adds relevant information about formats, sessions, full content, and truncation. It is dense but appropriately sized for a lookup tool with several important behavioral details.

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?

With no output schema, the description successfully explains the return shape and contents, including frontmatter, text, summaries, status, expanded full material, and pagination behavior. It gives an agent enough information to invoke and interpret the tool correctly.

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 the schema already documents all five parameters, giving a baseline of 3. The description still adds useful semantics for bill-number variants, session defaults, what full includes, and how max_chars truncation works.

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?

The description names a specific verb and resource: looking up one Georgia General Assembly bill or resolution by number. It clearly scopes the tool to a single item rather than a list or search, though it does not explicitly distinguish itself from the similar sibling bills_get_text.

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 gives clear usage context: bill numbers can appear in several written forms, and omitting session selects the newest regular session with that number while special-session bills may require naming the session. It also explains when to use full, but does not explicitly name alternatives such as bills_search or bills_get_text.

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