Skip to main content
Glama

Openstates

by io.github.pipeworx-io

Recent Changes

recent_changes
Read-onlyIdempotent

"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since since), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). since accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type. Only "company" supported today.
sinceYesWindow start — ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y"). Use "30d" or "1m" for typical monitoring.
valueYesTicker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly, openWorld, and idempotent hints. Description adds substantial context: fans out to SEC EDGAR, GDELT→GNews fallback, USPTO soft-fail due to PatentsView sunset, input formats, and return structure. No contradictions.

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 dense but every sentence provides necessary information: purpose, supported sources, fallback behavior, date formats, return shape, and alternative tool. It is well-structured with quotes for user intent and examples, earning its length.

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?

No output schema exists, so description compensates by specifying return structure (changes[] grouped by source, total_changes count, citation URIs). It also covers source-specific behaviors, failure modes, and input constraints, making the tool fully understandable without additional docs.

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?

Input schema has 100% coverage with useful descriptions, so baseline is 3. Description enhances this by giving examples (ISO vs relative shorthand), recommending '30d' or '1m' for typical monitoring, and explaining value can be ticker or zero-padded CIK. Adds practical guidance beyond schema.

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?

Description clearly identifies the tool as a change feed for a company over a time window, with specific verb ('change feed') and resource ('company'). It includes natural language triggers and explicitly differentiates from sibling tool entity_profile by contrasting dynamic changes vs static profile.

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?

Provides explicit when-to-use guidance with example queries and states the alternative: 'Use entity_profile instead when you want the static profile ... regardless of window.' Also explains parallel call benefit and fallback behavior between sources.

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

All Openstates toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation1/5

The tool set includes multiple pairs of nearly identical tools (e.g., ask_pipeworx and ask_pipeworx_grounded, bet_research and polymarket_arbitrage) that overlap heavily in purpose. Many tools also combine unrelated functions, making it difficult for an agent to select the right one without confusion.

Naming Consistency1/5

Tool names follow no discernible pattern: snake_case (ai_visibility_check), verb_noun (ask_pipeworx, get_bill), and even lengthy descriptive names (scan_competitor_ai_presence) are mixed. The naming style is chaotic and inconsistent across the set.

Tool Count2/5

With 30 tools, the count is excessive for a server supposedly focused on OpenStates (state legislatures). Only a few tools (search_bills, get_bill, etc.) relate to the server's name, while the rest are tangentially related to data lookups, betting, or AI visibility, making the set bloated.

Completeness1/5

The server's core domain (state legislative data) is severely underserved: only about 5 tools cover bills and legislators, lacking basic CRUD operations like create, update, or delete. Many obvious operations (e.g., searching bills by subject, tracking votes) are missing, while unrelated tools dominate.

Resources