Skip to main content
Glama

Fund Momentum

by io.github.schneidavie
OverviewDiscussionsAdmin

Search VC funds

search_funds
Read-onlyIdempotent

START HERE for any question about funds. Search actively deploying venture capital funds by stage, country and industry. COST: free, and it works with no API key at all. Returns name, slug, country, stage, fund size, industries and a durable profile URL. The slug in each result is what every other tool takes as input, so run this first and copy the slug rather than constructing one from a fund's name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to return (1-20)
stageNoFunding stage focus. Must be one of the listed enum values (lowercase, underscores). Common spellings such as 'Pre-Seed' or 'Series A' are accepted and normalised.
countryNoCountry of the fund's headquarters, spelled out in full (e.g. 'United States', 'United Kingdom', 'Germany'). Not an ISO code.
industryNoIndustry focus. Must be one of the listed enum values (lowercase, underscores), e.g. 'ai_ml', 'fintech', 'climate_sustainability'. Common spellings such as 'AI/ML', 'FinTech' or 'climate' are accepted and normalised.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / industry / description
      Previous value: -"Industry focus (e.g. 'AI/ML', 'FinTech', 'Climate')"New value: +"Industry focus. Must be one of the listed enum values (lowercase, underscores), e.g. 'ai_ml', 'fintech', 'climate_sustainability'. Common spellings such as 'AI/ML', 'FinTech' or 'climate' are accepted and normalised."
    • addedInput schema / properties / industry / enum
      Added value: +[
+  "agritech",
+  "ai_ml",
+  "biotech",
+  "built_environment",
+  "carbon_removal",
+  "circular_economy",
+  "climate_sustainability",
+  "cloud_devops",
+  "consumer_commerce",
+  "creator_economy",
+  "cybersecurity",
+  "data_infrastructure",
+  "deep_tech",
+  "defense",
+  "developer_tools",
+  "diagnostics",
+  "digital_banking",
+  "digital_education_consumer",
+  "digital_health",
+  "digital_infrastructure",
+  "ecommerce",
+  "energy_tech",
+  "enterprise_software",
+  "evs_charging",
+  "fashion_tech",
+  "fem_tech",
+  "fintech",
+  "food_beverage",
+  "food_tech",
+  "gaming",
+  "infrastructure_tech",
+  "insur_tech",
+  "iot",
+  "manufacturing",
+  "marketplaces",
+  "med_tech",
+  "mental_health",
+  "mobility_transport",
+  "payments_embedded_finance",
+  "private_markets",
+  "prop_tech",
+  "robotics_automation",
+  "saas",
+  "semiconductors",
+  "space",
+  "supply_chain",
+  "therapeutics",
+  "travel_tech",
+  "vertical_saas",
+  "water_tech",
+  "wealth_tech",
+  "web3_finance",
+  "web3_infrastructure",
+  "wellness_lifestyle"
+]
    • changedInput schema / properties / stage / description
      Previous value: -"Funding stage focus. Must be one of the listed enum values (lowercase, underscores)."New value: +"Funding stage focus. Must be one of the listed enum values (lowercase, underscores). Common spellings such as 'Pre-Seed' or 'Series A' are accepted and normalised."
  2. Changed4 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Country (e.g. 'United States', 'United Kingdom')"New value: +"Country of the fund's headquarters, spelled out in full (e.g. 'United States', 'United Kingdom', 'Germany'). Not an ISO code."
    • changedInput schema / properties / industry / description
      Previous value: -"Industry focus"New value: +"Industry focus (e.g. 'AI/ML', 'FinTech', 'Climate')"
    • changedInput schema / properties / limit / description
      Previous value: -"Number of results to return (max 20)"New value: +"Number of results to return (1-20)"
    • changedInput schema / properties / stage / description
      Previous value: -"Funding stage focus"New value: +"Funding stage focus. Must be one of the listed enum values (lowercase, underscores)."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark readOnly/idempotent/non-destructive, and the description adds meaningful context: it is free/no API key, returns a defined field set, and produces a durable profile URL plus slug. This goes beyond the schema but does not cover potential rate limits or ordering, which keeps it from a 5.

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

Conciseness5/5

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

The description front-loads the START HERE directive and filters, then adds cost/auth context and result-field details, with every sentence earning its place. It is slightly longer than minimal, but the slug-routing guidance is high-value.

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?

With no output schema, the description supplies the key return fields and the critical workflow fact (slug feeds other tools). Combined with high schema coverage and read-only annotations, an agent has everything needed to call this tool correctly.

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?

Schema covers 100% of parameters with clear descriptions, so description does not need to explain them. It restates stage/country/industry only as high-level filter dimensions and adds no syntax, enum normalization, or limit behavior 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?

The description states a specific action ('Search actively deploying venture capital funds') on a clear resource with filter dimensions (stage, country, industry). It also positions itself as the entry point to sibling tools via slug, distinguishing it from retrieval tools like get_fund.

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?

The description clearly instructs agents to start here for any fund question and to copy the slug for downstream tools, which is strong when-to-use guidance. It does not explicitly name sibling alternatives or state when to skip search (e.g., when a fund slug is already known).

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

All Fund Momentum toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources