Skip to main content
Glama
GMPSignal MCP Server

GMPSignal MCP Server

discover_startup_vc_dealflow

Read-onlyIdempotent

Aggregates YC, GitHub Trending, and Hacker News signals to surface high-traction early-stage startups and developer tools for venture deal-flow sourcing.

Instructions

Discover high-traction early-stage startups and open-source developer tools across Y Combinator (YC) cohorts, GitHub Trending repositories, and Hacker News Show/Launch discussions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sources": "<sources>"
    },
    "name": "discover_startup_vc_dealflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoSector, technology, or batch keyword (e.g., "AI agent", "MCP", "Fintech").AI
sourcesYesVenture deal-flow signal sources to aggregate.
maxResultsNoMaximum number of startup and repository traction records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.2

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety and external-data profile is covered. The description adds that results span three independent external sources, which explains why output is heterogeneous, but says nothing about freshness, rate limits, partial-source failures, or result ordering.

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?

A single front-loaded sentence with the verb first and the source list second — no filler or restated title. The three-source enumeration makes the sentence long but every element carries information.

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?

There is no output schema, so the description should say something about what a "record" looks like when three dissimilar sources are merged, and it does not. Given full schema coverage and complete annotations, the definition is callable but leaves the agent guessing at result shape and cross-source aggregation behavior.

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%, so the baseline is 3; the description earns a step above by naming the three concrete sources in prose, which reinforces the meaning of the `sources` enum as aggregatable signal feeds rather than abstract identifiers. It still adds nothing about how `query` matches titles versus descriptions or how `maxResults` interacts with per-source distribution.

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 uses a specific verb ("Discover") against three named resources (YC cohorts, GitHub Trending, Hacker News Show/Launch) plus the qualifier "high-traction early-stage startups." An agent knows exactly what corpus this tool aggregates, and no sibling in the catalog covers venture deal-flow, so discrimination is immediate.

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?

Usage is only implied by the word "Discover" and the deal-flow framing — an agent can infer this is a sourcing/lead-generation call. There is no explicit when-to-use, when-not-to-use, or mention of a complementary tool for, say, company enrichment or funding data.

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