Skip to main content
Glama
PrinceGabriel-lgtm

freshcontext-mcp

by PrinceGabriel-lgtm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

extract_finance_landscape

Read-only

Queries stock quotes, developer and investor discussions, GitHub activity, and product release velocity to generate a timestamped financial landscape report for specified tickers.

Instructions

Composite financial intelligence tool for developers. Given one or more ticker symbols, simultaneously queries: (1) Stooq for no-key quote data, (2) Hacker News for developer community sentiment, (3) Reddit for investor and tech community discussion, (4) GitHub for repo ecosystem activity around the company's tech, and (5) their product changelog for release velocity as a company health signal. Answers: What's the price? What are developers saying? Is the company actually shipping? Returns a unified 5-source timestamped report.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickersYesOne or more ticker symbols e.g. 'PLTR' or 'PLTR,MSFT,GOOG'. Up to 5 tickers.
max_lengthNo
company_nameNoCompany name for HN/Reddit/GitHub searches e.g. 'Palantir'. If omitted, derived from the ticker.
github_queryNoGitHub search query or repo URL for the company's tech ecosystem e.g. 'palantir' or 'https://github.com/palantir/foundry'. If omitted, uses company_name.
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

A3.8/5.0
Behavior4/5

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

Consistent with readOnlyHint and openWorldHint; describes read-only multi-source queries and a timestamped report. It does not contradict annotations, though it omits potential latency or rate-limit caveats.

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?

Uses a numbered source list and concise answer bullets, making the behavior easy to scan. Slight redundancy in phrasing ('simultaneously queries' and 'returns') but generally well structured.

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

Completeness3/5

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

No output schema is provided, yet the return value is only vaguely described as a unified 5-source timestamped report. The relationship between max_length, freshness_score, and the report structure is not explained, leaving some ambiguity for the agent.

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

Parameters3/5

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

Most parameters have solid schema descriptions, but max_length has no description and the tool description does not clarify it. With 80% schema coverage, the description adds limited meaning beyond the 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?

States a specific composite resource (finance landscape) and clearly identifies the multi-source approach, distinguishing it from source-specific siblings like extract_finance, extract_reddit, and extract_github.

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?

Describes what the tool queries and what questions it answers, but never explicitly states when to choose this over extract_finance or individual source tools; the use case is implied rather than directly guided.

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