Skip to main content
Glama

get_curated_act

Retrieve a curated reference record for a major US digital-asset act by slug, such as the GENIUS Act or CLARITY Act. Use the slug to get the requested act's details.

Instructions

Return a curated reference record for a major US digital-asset act by slug.

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": {
      "slug": "<slug>"
    },
    "name": "get_curated_act"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesWhich act to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. 'Return' suggests a read-only retrieval and 'curated reference record' indicates the output type, but the description does not address error behavior for invalid slugs, authentication needs, rate limits, or whether the record is static versus generated.

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 a single front-loaded sentence with no filler. Every phrase contributes to identifying the returned resource, its domain, and the lookup key.

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 one-parameter enum lookup, the description is sufficient to understand the basic call, but it does not describe what a 'curated reference record' contains. With no output schema, that leaves the return shape underspecified.

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 coverage is 100%, and the schema itself documents the single slug parameter with an enum and a description. The description repeats that the lookup is 'by slug' but adds no syntax, case, or format details beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource: 'Return a curated reference record' for a 'major US digital-asset act by slug.' It is clear what the tool does, but it does not explicitly differentiate itself from act-specific siblings such as get_clarity_act_info or get_genius_act_info.

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 slug parameter and enum imply when the tool is applicable, but the description gives no explicit when-to-use guidance, no exclusions, and no comparison with alternative act or regulation search tools.

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