Skip to main content
Glama

get_genius_act_info

Retrieves curated GENIUS Act (S.1582) reference details—status, timeline, sponsors, key provisions, agency jurisdiction, and source links—to support stablecoin legislation research.

Instructions

Curated reference for the GENIUS Act (Guiding and Establishing National Innovation for U.S. Stablecoins Act, S.1582, 119th Cong., Pub. L. 119-27). Returns status, timeline, sponsors, key provisions, agency jurisdiction, and source links. For live bill actions use get_bill_actions with billId 's1582-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_genius_act_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it identifies the tool as a curated reference rather than a live feed, and lists the categories of information returned. It does not cover permissions or rate limits, but for a read-only reference lookup that is a minor 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?

The description is two sentences, front-loaded with the resource identity and return scope, followed by the routing alternative. Every phrase adds value and nothing is wasted.

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 reference tool with no output schema, the description is sufficiently complete. It lists what the agent will receive and routes the agent away from using this for live bill actions, which is the main potential misuse case.

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 parameter semantics are not a meaningful risk. A baseline of 4 is appropriate; there is nothing for the description to explain beyond what the empty schema already conveys.

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 the exact resource (GENIUS Act), expands the acronym, provides citation details, and enumerates the returned content. It clearly distinguishes itself from the live-action sibling by stating that this is a curated reference and naming get_bill_actions as the alternative.

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

Usage Guidelines5/5

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

It explicitly states when to use this tool (curated reference information) and when to use an alternative (live bill actions via get_bill_actions with billId 's1582-119'). No inference is required about routing.

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