Skip to main content
Glama

get_clarity_act_info

Retrieves status, timeline, sponsors, key provisions, and SEC/CFTC jurisdiction details for the CLARITY Act (H.R.3633). Use it to understand this digital asset bill and its source links.

Instructions

Curated reference for the Digital Asset Market CLARITY Act (H.R.3633, 119th Cong.). Returns status, timeline, sponsor, key provisions, agency jurisdiction (SEC/CFTC), and source links. For live bill actions use get_bill_actions with billId 'hr3633-119'.

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_clarity_act_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden, and it does well: it declares the tool is a curated (non-live) reference and lists the returned content areas, which tells the agent not to expect fresh legislative actions. It does not state data currency, update cadence, or that the snapshot may lag the live record, which is the main remaining behavioral gap.

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?

Three tight sentences: identity, return contents, and alternative routing, in that order. Every clause carries information and the routing hint is front-loaded rather than buried.

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?

For a zero-parameter lookup with no output schema, the description compensates by enumerating the returned fields and pointing to the live-data sibling. An agent has everything needed to decide to call it and to interpret the response shape.

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?

The tool takes zero parameters, so no parameter meaning needs to be conveyed; the baseline of 4 applies. The description does confirm the bill identity inline (H.R.3633, 119th Cong.), which explains why no billId argument is required.

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?

The description names a specific resource (Digital Asset Market CLARITY Act, H.R.3633, 119th Cong.) and a specific verb (curated reference), then enumerates exactly what the reference contains: status, timeline, sponsor, provisions, SEC/CFTC jurisdiction, and source links. This is clearly distinguishable from siblings like get_genius_act_info or get_bill_details without opening a schema.

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 an explicit routing rule: for live bill actions, use get_bill_actions with billId 'hr3633-119'. That is a concrete when-to-use-elsewhere instruction with the exact parameter value supplied. It stops short of clarifying how this differs from get_curated_act or get_bill_details, so the alternative set is only partially mapped.

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