Skip to main content
Glama

get_legislative_intelligence_synthesis

Read-only

Legislative intelligence synthesis: current bill status, recent passages, and amendments for a topic and jurisdiction, synthesized from live sources with a cryptographic receipt. $1.00 USDC per call.

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": {
      "topic": "<topic>"
    },
    "name": "get_legislative_intelligence_synthesis"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYes
jurisdictionNo

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 read-only, open-world, and non-destructive, so the description adds value by disclosing that results are synthesized from live sources, accompanied by a cryptographic receipt, and billed at $1.00 USDC per call — pricing and provenance are genuinely useful behavioral facts. It stops short of describing latency, recency windows, or failure behavior for a paid open-world lookup.

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?

A single dense sentence, front-loaded with the resource and outputs, followed by provenance and the price. Every clause carries information an agent needs, with no filler.

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?

With no output schema and an open-world paid call, the description should say more about what the synthesis actually returns (structure, recency, source mix) and how jurisdiction values are expressed. It is complete enough to select the tool and form a call, but not enough to predict the response.

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 0%, so the description has to carry parameter meaning; it does name both the topic and jurisdiction dimensions, which maps to the two parameters. However, it gives no format guidance for jurisdiction (free-form string with no enum, e.g. state code vs. country) and no hint about topic granularity, so meaning beyond the schema is thin.

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-plus-resource ('Legislative intelligence synthesis') and enumerates the content produced: current bill status, recent passages, and amendments, scoped to a topic and jurisdiction. It is clearly distinguishable from adjacent synthesis tools such as case-law or regulatory-news, though it never names an alternative explicitly.

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?

Usage is only implied: an agent can infer this is the tool for tracking bills and amendments in a given jurisdiction on a topic. There is no statement of when not to use it, no prerequisites, and no routing to sibling synthesis tools, so guidance is adequate but bare.

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