Skip to main content
Glama

get_public_law_text

Fetch a U.S. Public Law package from GovInfo by Congress and law number, returning a summary and optional truncated plain text for legal research.

Instructions

Fetch a Public Law package from GovInfo (summary + optional truncated plain text). Example: congress=119, lawNumber=27 returns the GENIUS Act.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "congress": "<congress>",
      "lawNumber": "<lawNumber>"
    },
    "name": "get_public_law_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
congressYesCongress that enacted the law (e.g., 119).
maxCharsNoTruncation length for inline text (default 20000).
lawNumberYesPublic law number within that Congress (e.g., 27 for 119-27).
includeTextNoWhether to also fetch and include the law text (truncated). Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden. It does useful work by stating that text is truncated and that plain text is optional, but it omits whether auth/API keys are needed, what happens when the law number does not exist, and whether errors or empty results are returned.

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?

Two front-loaded sentences: the first states what is fetched and what is returned, the second grounds it in a concrete example. No filler and nothing redundant with the schema.

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?

For a simple four-parameter read tool with no annotations and no output schema, the description covers the essential shape of the response (summary plus truncated text). It would be stronger if it stated failure behavior for a nonexistent law and roughly what the summary contains.

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 all four parameters including defaults and ranges. The description only reinforces this with a concrete example (congress=119, lawNumber=27) and the truncation concept behind maxChars, so the baseline of 3 is appropriate.

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 ("Fetch a Public Law package from GovInfo") and scopes the payload (summary plus optional truncated plain text). It is clearly distinct from bill-oriented siblings such as get_bill_text, though it never names an alternative directly.

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?

The GovInfo/Public Law framing and the congress+lawNumber example imply when this tool applies, but there is no explicit when-to-use or when-not guidance and no routing to alternatives like get_bill_text or get_curated_act. An agent must infer the selection criteria.

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