Skip to main content
Glama

Fund Momentum

by io.github.schneidavie
OverviewAdmin

Search VC funds

search_funds
Read-onlyIdempotent

Search actively deploying venture capital funds by stage, country, and industry. Free tier. Returns name, slug, country, stage, fund size, industries and a durable profile URL.

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. Dates show when Glama detected each change.

  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/5.0
Behavior4/5

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

Light annotations already indicate a non-destructive read operation. The description adds useful transparency with details about the free tier, the 'actively deploying' qualification, and the returned fields including the durable profile URL. This goes beyond the annotations without contradicting them.

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 is concise and front-loaded with the core purpose, followed by one compact sentence covering expectations and output. No filler or redundant material.

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?

The tool is straightforward and the schema provides detailed parameter guidance. The description sufficiently covers the output contract by listing the return fields and durable profile URL. Minor optional additions such as pagination behavior are absent but not essential for correct invocation.

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?

The input schema is fully described, including enums, descriptions, and normalization notes. The description only restates the high-level filter concepts at a general level, adding no material 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?

The description begins with a specific action ('Search') and resource ('venture capital funds'), and immediately scopes the purpose with filter dimensions: stage, country, and industry. It is clearly distinguishable from sibling tools like get_fund and get_fund_signals, which suggest different actions.

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 makes the core use case clear — discovering actively deploying funds by filters. However, it does not explicitly state when to prefer this tool over alternatives such as get_fund, or provide exclusions to guide selection among siblings.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources