Skip to main content
Glama
PrinceGabriel-lgtm

freshcontext-mcp

by PrinceGabriel-lgtm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

extract_gov_landscape

Read-only

Analyze a company's government contract awards, development activity, and community visibility by combining USASpending, GitHub, Hacker News, and product changelog data into a unified timestamped report.

Instructions

Composite government intelligence tool. Given a company name, keyword, or NAICS code, simultaneously queries: (1) USASpending.gov for federal contract awards, (2) GitHub for the company's repo activity, (3) Hacker News for developer community awareness, and (4) their product changelog for release velocity. Answers: Who is winning government contracts in this space? Are they actually building? Does the dev community know about them? Returns a unified 4-source timestamped report. Unique — not available in any other MCP server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesCompany name (e.g. 'Palantir'), keyword (e.g. 'artificial intelligence'), or NAICS code (e.g. '541511'). For GitHub and changelog sections, also optionally provide a GitHub URL.
github_urlNoOptional GitHub repo URL for the company (e.g. 'https://github.com/palantir/palantir-java-format'). If omitted, GitHub and changelog sections use the query as a search term.
max_lengthNo
min_freshness_scoreNoFilter sections below this freshness_score (0–100). E.g. 70 = only recently retrieved data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.1
    • addedInput schema / properties / min_freshness_score
      Added value: +{
+  "description": "Filter sections below this freshness_score (0–100). E.g. 70 = only recently retrieved data.",
+  "type": "number"
+}
  2. First observedv0.3.12

TDQS

A4.1/5.0
Behavior4/5

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

The description discloses key behaviors not covered by annotations: it 'simultaneously queries' four sources and 'returns a unified 4-source timestamped report'. It also hints at size/freshness controls via max_length and min_freshness_score. No contradictions with the readOnlyHint or openWorldHint annotations.

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 structured with a clear lead ('Composite government intelligence tool'), numbered source list, and purpose statement. It is slightly verbose with the marketing claim 'Unique — not available in any other MCP server', but the structure helps readability.

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

Completeness4/5

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

Given the tool's composite complexity and lack of an output schema, the description adequately explains what it queries, why, and what it returns. It also clarifies how parameters affect sections. A more detailed output structure or error behavior would improve completeness, but it's not critically missing.

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?

The schema describes three of four params; the description adds essential context for query (company/keyword/NAICS) and github_url (optional, scopes GitHub/changelog sections). max_length lacks a description but its name and default are self-explanatory, and the overall description compensates for the 75% coverage.

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 is a 'Composite government intelligence tool' and enumerates the four data sources (USASpending, GitHub, Hacker News, changelog) and the questions it answers. It distinguishes itself from more focused siblings like extract_govcontracts or extract_hackernews by covering multiple sources in one call.

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

Usage Guidelines3/5

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

The description implies when to use it—when a broad multi-source government intelligence snapshot is needed—by listing the integrated sources and output. However, it does not explicitly state 'use this when…' or contrast with alternatives, leaving the decision to the agent's inference.

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

Deploy Server

Other Tools