Skip to main content
Glama

Usaspending

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").

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Despite annotations already declaring readOnlyHint, openWorldHint, etc., description adds rich behavioral context: fans out to multiple sources with fallback logic (GDELT→GNews), notes USPTO patent soft-fail, and describes return structure (changes[] grouped by source + total_changes + citation URIs). No contradiction with annotations.

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?

Description is front-loaded with example queries, then explains mechanics. Every sentence provides useful information, no fluff. Length is justified by complexity of the tool.

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?

Given the tool's multi-source nature, fallback logic, and no output schema, the description adequately covers all aspects: input parameters, sources queried, fallbacks, return format, and even notes a limitation (USPTO patents soft-fail). Leaves no ambiguity for an agent.

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 covers all 3 parameters with descriptions. Description adds value by providing practical examples for `since` (ISO date and relative shorthand like '7d', '30d'), explains `value` can be ticker or CIK, and clarifies `type` is only 'company'. Does not fully repeat schema but enhances it.

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 the tool provides a change feed for a company across multiple sources in one parallel call. It gives specific example queries and distinguishes from sibling tool 'entity_profile' which provides 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?

Explicitly states when to use this tool (dynamic changes over a window) vs when to use entity_profile (static profile). Provides example queries like 'What's new with X' and explains the window parameter.

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

All Usaspending 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.8/5.0
Disambiguation2/5

ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are essentially the same router with different output modes, and ask_pipeworx_beta is currently identical to ask_pipeworx. There is also meaningful overlap between entity_profile, compare_entities, recent_changes, validate_claim, and the USAspending profile/search tools.

Naming Consistency3/5

All names are lower_snake_case with useful prefixes like ask_, polymarket_, and usa_, which helps grouping. However, the underlying convention is mixed: some are verb+object, some are noun phrases, and some are bare verbs, so there is no uniform verb_noun pattern.

Tool Count2/5

38 tools is well beyond the heavy range, and most of them are unrelated to USAspending: Polymarket betting, npm dependency checks, AI visibility, memory storage, and meta-tools. The actual USAspending-specific surface is only about seven tools, making the server feel bloated and unfocused.

Completeness3/5

The federal-contract cluster covers award search, recipient/incumbent profiles, expiring awards, and spending by agency/category/trend, which handles the main contracting questions. Missing award-detail retrieval, grants/assistance coverage, and open-solicitation lookup, which usa_expiring_awards explicitly punts to external samgov/govcon tools.

Resources