Skip to main content
Glama
sec-edgar-fda-b2b-mcp

sec-edgar-fda-b2b-mcp

get_yc_startups

Read-onlyIdempotent

Search funded Y Combinator startups by industry or keyword to support B2B lead generation, VC deal sourcing, and startup market research. Returns company details for up to 100 matches.

Instructions

Search funded Y Combinator startups by industry, keyword, batch, and hiring status.

Use this tool for B2B lead generation, VC deal sourcing, and startup market research.
Returns a JSON array of up to 25 companies containing companyName, batch, website,
oneLiner, teamSize, isHiring, and industries. Requires the APIFY_TOKEN environment variable.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_yc_startups"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_resultsNoMaximum number of Y Combinator startup profiles to return (1-100).
industry_or_keywordNoIndustry, vertical, or keyword to filter Y Combinator startups (e.g., 'AI', 'B2B', 'Fintech').AI

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / industry_or_keyword / description
      Added value: +"Industry, vertical, or keyword to filter Y Combinator startups (e.g., 'AI', 'B2B', 'Fintech')."
    • addedInput schema / properties / max_results / description
      Added value: +"Maximum number of Y Combinator startup profiles to return (1-100)."
    • addedInput schema / properties / max_results / maximum
      Added value: +100
    • addedInput schema / properties / max_results / minimum
      Added value: +1
  2. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds useful information about the APIFY_TOKEN requirement and returned company fields. However, it says the tool returns up to 25 companies while the schema allows max_results up to 100, and this cap claim is misleading.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and reasonably short. However, it spends words on unsupported filters and an inaccurate result cap, which reduces trust and precision rather than adding value.

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?

The tool is simple with two parameters, full schema descriptions, annotations, and an output schema. The description covers purpose, use cases, and authentication, but its incorrect filter claims and result-size limit leave it partially incomplete and misleading.

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

Parameters2/5

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

Schema coverage is 100%, so the baseline would normally be 3. But the description claims filters for batch and hiring status that do not exist in the schema, which can mislead an agent into expecting unsupported filtering. It also does not clarify the relationship between max_results and the stated 25-company return cap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb and resource: searching funded Y Combinator startups. It distinguishes the tool from siblings like SEC and FDA data tools. However, it overstates the supported filters by naming batch and hiring status, which are not present in the schema.

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

Usage Guidelines4/5

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

It gives explicit use cases: B2B lead generation, VC deal sourcing, and startup market research. It does not name alternatives or exclusions, but the context is clear enough for an agent to know when this tool is appropriate.

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