Skip to main content
Glama

policypulse

Track and analyze global legislation with bill summaries, sector impact, and compliance guidance. Monitor US Congress, EU, UK, and 50+ jurisdictions for policy changes.

Instructions

PolicyPulse: PolicyPulse — global legislative intelligence: US Congress, EU (EUR-Lex), UK Parliament, India, Brazil, Australia, and 50+ jurisdictions. Bill summaries, sector impact, passage probability, treaty ana

Coverage: Global

Endpoints: • legislation ($0.10): Legislation — plain English translation of any bill globally • impact ($0.10): Impact — who is affected and what they must do • scenario ($0.10): Scenarios — if/then sector impact modeling • monitor ($0.10): Monitor — weekly/monthly legislative activity brief • state ($0.10): State — legislation across all 50 US states via Open States • compliance ($0.10): Compliance — what to do after a law passes • regulation ($0.10): Federal regulation — agency rules via Federal Register • compare ($0.10): Compare — cross-jurisdiction policy comparison • calendar ($0.10): Calendar — upcoming regulatory deadlines and effective dates • translate ($0.10): Translate — decode any legal or regulatory text into plain English

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoaction
langNoResponse language (ISO 639-1 code)
qNoBill name or topic (e.g. 'NLRB joint employer rule', 'ACA employer mandate', 'EU AI Act')
jurisdictionNojurisdiction
sectorNoSector focus (or 'all')
entity_typeNoFilter to specific entity type (e.g. 'employer under 50 employees')
triggerNoThe development to model (e.g. 'federal $15 minimum wage passes', 'FTC non-compete ban upheld', 'California single-payer healthcare enacted'
periodNoperiod
topicNotopic
stateNo2-letter state code (TX) or comma-separated list (CA,TX,NY)
lawNoLaw or regulation (e.g. 'OSHA heat stress standard', 'ADA', 'California CCPA', 'FTC non-compete ban')
agencyNoFederal agency (EPA|FDA|OSHA|FTC|CFPB|SEC|DOL|USDA|HHS|FCC|etc)
jurisdictionsNoComma-separated jurisdictions (e.g. 'US,EU,UK,Canada,Australia')
lookaheadNoDays ahead to surface deadlines
textNoLegal or regulatory text to decode (up to 4,000 chars; use POST for longer text)
contextNocontext
Behavior2/5

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

With no annotations, the description should disclose traits like read-only nature, authentication, or rate limits. It only lists endpoints and costs, not behavioral effects or safety profiles.

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 description is structured with a list of endpoints and costs, but it is lengthy, repeats 'PolicyPulse:', and includes unnecessary formatting. It could be more concise.

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, the description gives an overview of capabilities and endpoints, but lacks details on what each endpoint returns and how to combine parameters effectively. It is adequate but not complete.

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%, so the baseline is 3. The description adds little to parameter understanding—it lists endpoints but does not clarify how the 'action' parameter maps to them or how other parameters should be used together.

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 clearly states that PolicyPulse is a global legislative intelligence tool covering many jurisdictions and providing analyses like bill summaries and passage probability. It distinguishes from sibling tools by its policy focus, though it encompasses many sub-actions.

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

Usage Guidelines2/5

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

The description does not provide guidance on when to use this tool versus the many sibling pulse tools. It lists endpoints but no conditions or exclusions for use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GTCC777/pulsenetwork-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server