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, industry and recent closes. Works with no API key at all (keyless trial); see the Cost line at the end for per-fund pricing on agent credits. Returns name, slug, country, stage, fund size, industries, the latest published close (lastCloseDate, lastCloseType) and a durable profile URL. For 'which funds just closed', pass closed_since: results then come newest close first. 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. Cost: 1 credit per fund returned (EUR 0.01 each). Default limit 10. Default max_credits 10, hard maximum 25 per call. Billed per fund for agent credits and inline MPP only; Starter and Pro are flat-fee and the keyless trial is free. The cost of each call is reported in the response's billing object.

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results to return. Default 10 for every caller, including agents paying with credits and subscribers, so an omitted limit never returns or bills more than 10 funds. Without a paid account the maximum is 10; a larger value is rejected, not clamped. Agents paying with credits are billed 1 credit (EUR 0.01) per fund returned, up to 150 funds per key per UTC day (a call that would exceed the remainder is refused before any charge); pass a larger limit explicitly to receive more. Starter gets up to 50 per call; Pro gets up to 250 and can page with offset. The response reports `matched` (total matches) and `truncated`.
stageNoFunding stage. Matches every fund that invests at this stage, including multi-stage funds whose range covers it (each result lists all its stages in fundingStages). Must be one of the listed enum values (lowercase, underscores). Common spellings such as 'Pre-Seed' or 'Series A' are accepted and normalised.
offsetNoNumber of matches to skip, for paging through a large result set (use next_offset from a truncated response). Agents paying with credits and Pro plans only.
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.
max_creditsNoOptional spending ceiling for this call, in credits (1 credit = EUR 0.01). Rows returned never exceed floor(max_credits / credits per row). Omitted: the ceiling is the cost of the effective limit (10 credits for the default page). Values above 25 are clamped to 25; zero, negative and non-integer values are rejected before anything is charged. It is a clamp on limit only and does not apply to Starter or Pro. When it cuts the page, the response has truncated: true and truncated_reason: "max_credits".
closed_sinceNoOnly funds whose latest published close (first, interim or final close, or a launch) is on or after this date, ISO format YYYY-MM-DD (e.g. '2026-09-01'). Close data comes from Fund Momentum's own close coverage, each with a source URL in get_fund's last_close block.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / max_credits
      Added value: +{
+  "description": "Optional spending ceiling for this call, in credits (1 credit = EUR 0.01). Rows returned never exceed floor(max_credits / credits per row). Omitted: the ceiling is the cost of the effective limit (10 credits for the default page). Values above 25 are clamped to 25; zero, negative and non-integer values are rejected before anything is charged. It is a clamp on limit only and does not apply to Starter or Pro. When it cuts the page, the response has truncated: true and truncated_reason: \"max_credits\".",
+  "minimum": 1,
+  "type": "integer"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Number of results to return. Without a paid account the maximum is 10 (default 10); a larger value is rejected, not clamped. Agents paying with credits are billed 1 credit (EUR 0.01) per fund returned, up to 150 funds per key per UTC day (a call that would exceed the remainder is refused before any charge); if limit is omitted they receive every match within that allowance. Starter gets up to 50 per call; Pro gets up to 250 and can page with offset. The response reports `matched` (total matches) and `truncated`."New value: +"Number of results to return. Default 10 for every caller, including agents paying with credits and subscribers, so an omitted limit never returns or bills more than 10 funds. Without a paid account the maximum is 10; a larger value is rejected, not clamped. Agents paying with credits are billed 1 credit (EUR 0.01) per fund returned, up to 150 funds per key per UTC day (a call that would exceed the remainder is refused before any charge); pass a larger limit explicitly to receive more. Starter gets up to 50 per call; Pro gets up to 250 and can page with offset. The response reports `matched` (total matches) and `truncated`."
  3. Changed1 schema field changed
    • changedInput schema / properties / stage / description
      Previous 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."New value: +"Funding stage. Matches every fund that invests at this stage, including multi-stage funds whose range covers it (each result lists all its stages in fundingStages). Must be one of the listed enum values (lowercase, underscores). Common spellings such as 'Pre-Seed' or 'Series A' are accepted and normalised."
  4. Changed1 schema field changed
    • addedInput schema / properties / closed_since
      Added value: +{
+  "description": "Only funds whose latest published close (first, interim or final close, or a launch) is on or after this date, ISO format YYYY-MM-DD (e.g. '2026-09-01'). Close data comes from Fund Momentum's own close coverage, each with a source URL in get_fund's last_close block.",
+  "format": "date",
+  "type": "string"
+}
  5. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Number of results to return. Without a paid account the maximum is 10 (default 10); a larger value is rejected, not clamped. Paying callers have no maximum and, if limit is omitted, receive every match. The response reports `matched` (total matches) and `truncated`."New value: +"Number of results to return. Without a paid account the maximum is 10 (default 10); a larger value is rejected, not clamped. Agents paying with credits are billed 1 credit (EUR 0.01) per fund returned, up to 150 funds per key per UTC day (a call that would exceed the remainder is refused before any charge); if limit is omitted they receive every match within that allowance. Starter gets up to 50 per call; Pro gets up to 250 and can page with offset. The response reports `matched` (total matches) and `truncated`."
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Number of matches to skip, for paging through a large result set (use next_offset from a truncated response). Agents paying with credits and Pro plans only.",
+  "type": "integer"
+}
  6. Changed2 schema fields changed
    • removedInput schema / properties / limit / default
      Removed value: -10
    • changedInput schema / properties / limit / description
      Previous value: -"Number of results to return (1-20)"New value: +"Number of results to return. Without a paid account the maximum is 10 (default 10); a larger value is rejected, not clamped. Paying callers have no maximum and, if limit is omitted, receive every match. The response reports `matched` (total matches) and `truncated`."
  7. 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."
  8. 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)."
  9. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, so the safety profile is covered. The description goes well beyond that with the economics that actually constrain a call: 1 credit per fund returned, a keyless free tier, per-call defaults and hard caps, and a billing object in the response. The cross-reference of limits to the plan tiers is a bit tangled (the schema carries the authoritative version), but the behavioral picture is clear.

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?

Front-loaded with the highest-value directive ('START HERE'), and each paragraph covers one concern: what it does, how to use the slug, cost. It loses a point because the Cost paragraph duplicates defaults and caps that the schema already states in more precise form ('Default limit 10. Default max_credits 10, hard maximum 25 per call').

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?

Seven all-optional parameters, no output schema, yet the description enumerates the returned fields (name, slug, country, stage, fund size, industries, lastCloseDate, lastCloseType, durable URL), names the routing convention, and spells out the cost model. An agent has everything to decide, call, and interpret the response without opening the schema.

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 above-baseline for two things the schema doesn't state: closed_since returns results newest-close-first, and the slug it returns is the input every other tool requires. It also flags the close definitions (first/interim/final, or a launch) rather than relying on the schema's date format alone.

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 verb and resource ('Search actively deploying venture capital funds') plus the dimensions it filters on, and immediately distinguishes itself from siblings by declaring itself the entry point ('START HERE for any question about funds'). An agent can tell this is the discovery tool and get_fund/search_lps are not.

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

Usage Guidelines5/5

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

Explicit when-to-use ('START HERE for any question about funds'), a conditional branch ('For which funds just closed, pass closed_since'), and a dependency rule tying it to every other tool ('run this first and copy the slug rather than constructing one from a fund's name'). It says when this tool is the right call and how its output feeds 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
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