Skip to main content
Glama

get_us_state_ai_legislation

Read-only

Use when mapping AI regulatory compliance obligations across multiple states, advising on jurisdiction-specific AI deployment requirements, or briefing legal and compliance teams on the US state AI legislation landscape. As of May 2026, Colorado (June 30), Illinois, Texas, California, Virginia, and 9 additional states have enacted or advanced material AI legislation — creating a patchwork of obligations for multi-state AI deployments without a federal standard. Example: Financial institution deploying AI in 12 states faces 4 distinct compliance regimes with conflicting definitions of high-risk AI — multi-state compliance cost estimated $800K-$2M annually for mid-size institutions. Source: NCSL + Stratalize Regulatory Intelligence. $0.10 USDC per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_us_state_ai_legislation"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoState name or 2-letter abbreviation. Omit for national summary of all states.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuinely useful context beyond that: data currency ('As of May 2026'), enumerated state coverage, the underlying source (NCSL + Stratalize Regulatory Intelligence), and a per-call price of $0.10 USDC. It does not disclose the shape of the response, but for a read-only lookup tool this is a solid addition.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The leading 'use when' clause is front-loaded and effective, but the example scenario with $800K–$2M cost figures, the source attribution, and the pricing line read as marketing padding that does not help an agent decide or invoke. Roughly half the text is persuasive framing rather than operational guidance.

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?

For a single-parameter, annotation-covered lookup, the description covers when to use, data currency, and coverage breadth. However, with no output schema, it says nothing about what a call actually returns — bill status, effective dates, obligation categories, or coverage per state — leaving the agent to guess the payload's usefulness.

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?

With one optional parameter at 100% schema description coverage, the schema already explains that a state name or 2-letter abbreviation is accepted and that omitting it yields a national summary. The description adds no syntax, format, or usage nuance for the parameter beyond implying multi-state context in its examples, so it neither compensates for nor improves on the schema.

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 makes clear this tool covers US state-level AI legislation, naming the resource and the states involved (Colorado, Illinois, Texas, California, Virginia, plus 9 more). It frames purpose through use cases rather than a direct verb+object statement, but an agent can still tell it retrieves state AI legislative/regulatory status. It does not explicitly contrast with sibling tools like get_colorado_ai_act_requirements or get_eu_ai_act_coverage, even though Colorado is named as a covered state.

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?

Three explicit 'use when' scenarios are given: multi-state compliance mapping, jurisdiction-specific deployment advising, and legal/compliance briefing. This is strong positive guidance, but there is no when-not guidance and no named alternative (e.g., use get_colorado_ai_act_requirements for Colorado-specific depth), so the agent must infer sibling boundaries from names alone.

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.

Resources