Skip to main content
Glama

policypulse

Monitor and analyze global legislation from 50+ jurisdictions. Get bill summaries, sector impact, passage probabilities, and compliance guidance in plain English.

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.15): Legislation — plain English translation of any bill globally • impact ($0.15): Impact — who is affected and what they must do • scenario ($0.20): 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.15): Compliance — what to do after a law passes • regulation ($0.15): Federal regulation — agency rules via Federal Register • compare ($0.15): Compare — cross-jurisdiction policy comparison • calendar ($0.10): Calendar — upcoming regulatory deadlines and effective dates • translate ($0.08): Translate — decode any legal or regulatory text into plain English • court ($0.15): Court decision intelligence • treaty ($0.10): International treaty and trade-agreement intelligence

Input Schema

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

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

No annotations provided. The description does not disclose behavioral traits such as authentication, rate limits, or whether the tool is read-only. It only lists endpoints and costs, which does not add behavioral context beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose and cluttered with pricing and a long list of endpoints. Key purpose is not front-loaded, and excessive details detract from conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 19 parameters and no output schema or annotations, the description is incomplete. It fails to explain how parameters map to endpoints, what outputs to expect, or any behavioral nuances, leaving significant gaps for an agent.

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 100%, so baseline is 3. The description does not add meaning beyond the schema; it lists endpoints separately without linking them to parameters. It neither improves nor significantly worsens understanding of parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description lists multiple endpoints and pricing but does not clearly state what the tool does as a whole. It calls it 'global legislative intelligence' but does not differentiate it from sibling tools like legalpulse or taxpulse, making it vague.

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?

No guidance on when to use this tool versus alternatives. The description lists endpoints but does not explain when to choose each, nor does it mention when not to use the tool.

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/mcp-pulsenetwork'

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