Skip to main content
Glama

Samgov

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?

The description adds significant context beyond annotations: explains fallback logic (GDELT preferred, GNews when rate-limited/5xx), USPTO API sunset soft-failure, accepted date formats and recommendations, and return structure with grouped changes, total count, and citation URIs.

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?

The description is comprehensive but slightly lengthy. It front-loads the core purpose and examples efficiently, but every sentence earns its place. A minor reduction for verbosity; still very well-structured.

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 has 3 parameters, no output schema, and no nested objects, the description is thorough. It covers data sources, error handling, return format, and sibling differentiation, ensuring an agent can use it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All three parameters have schema descriptions (100% coverage). The description adds further value: for 'since' it gives examples and recommends '30d' or '1m', for 'value' it clarifies ticker or CIK format, and for 'type' it confirms only 'company' supported.

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?

The description clearly states the tool provides a 'change feed for a company in the last N days/weeks/months' and gives specific examples like 'What's new with X' and 'latest on Y'. It lists data sources (SEC, GDELT/GNews, USPTO) and explicitly distinguishes itself from the sibling tool '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 Guidelines5/5

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

The description provides explicit usage examples and a clear 'when not to use' directive: 'Use entity_profile instead when you want the static profile... regardless of window'. It also explains fallback behavior between GDELT and GNews, and notes soft-failure for USPTO.

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

All Samgov 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

Three ask_pipeworx variants and a dense cluster of polymarket_* edge tools have heavily overlapping purposes, and ai_visibility_check vs scan_competitor_ai_presence further blurs boundaries. Only the sam_*, memory, and subscription tools form cleanly distinct families.

Naming Consistency3/5

All names are lowercase snake_case and readable, but the pattern is mixed: verb_noun names (compare_entities, resolve_entity), bare verbs (remember, recall, forget), noun phrases (entity_profile, polymarket_edges), and domain-prefix families (sam_*, polymarket_*) coexist. No camelCase chaos, but no consistent verb style either.

Tool Count2/5

36 tools is well beyond the ideal range, and many are near-duplicates or wrappers (ask_pipeworx variants, ai_visibility_check vs scan_competitor_ai_presence). The server is named Samgov, yet only 5 tools actually concern SAM.gov, making the count feel inflated and unfocused.

Completeness3/5

The SAM.gov subset covers entity search, opportunities, set-asides, opportunity details, and exclusions, but omits major datasets like contract awards. The broader Pipeworx research/memory/subscription surface is extensive, though it is muddled by redundant query modes and lacks a direct way to invoke individual pack tools.

Resources