Skip to main content
Glama

Senate Lobbying

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.4/5.0
Behavior4/5

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

Discloses parallel calls, fallback from GDELT to GNews, and soft-failure for USPTO. Annotations already declare readOnlyHint, idempotentHint, destructiveHint false; description adds operational detail without contradiction.

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

Conciseness4/5

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

Description is about 100 words, front-loaded with example queries, and every sentence adds value (source details, parameter nuances, sibling reference). Concise for the complexity.

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?

Despite no output schema, description adequately describes return structure (changes[] grouped by source, total_changes count, citation URIs). Covers data sources, fallback, soft-fail, and parameter specs fully.

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?

Schema coverage is 100% (baseline 3), but description adds meaning: explains 'since' accepts ISO or relative formats with examples, clarifies 'value' can be ticker or CIK, and notes 'type' is currently limited to 'company'.

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 states tool provides a 'change feed for a company' aggregating from SEC, GDELT/GNews, USPTO. Specific verbs like 'fans out' and 'returns structured changes' clarify the action. Distinguishes from sibling entity_profile.

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

Usage Guidelines4/5

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

Provides explicit usage examples ('What's new with X', etc.) and advises using entity_profile for static profiles. Gives parameter guidance for 'since'. Lacks explicit when-not-to-use scenarios.

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

All Senate Lobbying 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

A3.6/5.0
Disambiguation2/5

There are several near-duplicate clusters: ask_pipeworx, ask_pipeworx_beta (explicitly described as currently identical), ask_pipeworx_grounded, deep_research, and validate_claim all route to the same underlying data; the six Polymarket tools (bet_research, arbitrage, edges, edge_tracker, fill_risk, kalshi_spread) heavily overlap in purpose and are easy to confuse. Even detailed descriptions do not fully resolve which tool an agent should pick first.

Naming Consistency3/5

All names use snake_case and many follow a verb_noun pattern (search_filings, get_filing, list_issue_codes, resolve_entity), but there is a mix of verb-first names (ask_pipeworx, compare_entities, generate_llms_txt), noun-first names (recent_changes, entity_profile, pipeworx_trending), and brand-prefixed families (pipeworx_*, polymarket_*). The naming is readable but not a single predictable pattern.

Tool Count2/5

A server named 'Senate Lobbying' exposes 34 tools, but only three (search_filings, get_filing, list_issue_codes) relate to LDA lobbying data. The remaining 31 cover generic Pipeworx data lookup, prediction markets, memory, subscriptions, AI visibility, and npm package audits—an extreme overreach for the apparent scope and likely to confuse an agent expecting a focused lobbying toolkit.

Completeness2/5

For the lobbying domain implied by the server name, only search, get-one-filing, and issue-code enumeration exist; there is no aggregation/stats tool, no lobbyist/client entity resolution for LDA, no registrant or foreign-entity browsing, and no coverage of related concepts like lobbying firm hierarchies or spending trends. The generic Pipeworx tools fill a different domain, so the lobbying-specific surface has significant gaps.

Resources