Fund Momentum

Request a warm intro

request_warm_intro

Idempotent

Ask Michael for a warm intro to a fund or an LP. Fulfilled BY HAND through the same queue and Slack notification the website's own "Request a warm intro" button uses -- this is not an automated connection and carries no guaranteed timeline. A known match (get_fund's or search_lps' michael_network.has_warm_path) is a PRECONDITION: intros are only sold where Michael's network already has a path, exactly like the website. For a target without one nothing is sold: the call creates a FREE path check instead (status "pending_review", charged: false). Michael then checks his own network by hand; only if he finds a path does the account holder decide on https://fundmomentum.vc/intro-credits whether to spend one credit. No path means no charge, and an unanswered check closes automatically after 14 days. Asking again about a target you already asked about is free and returns the existing status; only a genuinely new request is charged. COST: EUR 50 per intro, flat -- the identical per-unit price a human pays on the intro-credits page: pay exactly quantity times EUR 50. No agent discount, and NO subscription tier (human or Pro) ever makes an intro free -- Free/Starter/Pro/LP Radar unlock visibility only (get_fund, check_lp_coverage, search_lps); an actual intro always costs, on a per-user/per-type credit balance for a human's own key, or on agent credits/MPP at this same price for an agent key. IDENTITY REQUIRED: unlike every other tool here, this one needs someone to contact, because Michael reviews and fulfills every request by hand. A human's own API key works directly. An agent key must first be linked to a human account (POST to /_api/agent/link; see the server card) -- an unlinked agent key is refused here before anything is charged. Cost: EUR 50.00 per intro, flat. Never included in any plan (Free, Starter, Pro or Enterprise); a human key spends its intro-credit balance, an agent key pays per call at the same price. Re-asking about a target already requested is free.

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": {
      "target_type": "<target_type>",
      "slug": "<slug>"
    },
    "name": "request_warm_intro"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes	The slug of the LP (from search_lps or check_lp_coverage's referral) or the fund (from search_funds, match_startup or get_fund), exactly as returned by that tool. Not guessed from a display name.
`contact`	No	Optional. The named person at the target you want to be introduced to (max 80 characters), e.g. "Jane Doe".
`context`	No	Optional. Short note for Michael: what is being raised, how you are connected, timing (max 1000 characters). Used only when a path check is created.
`target_type`	Yes	Whether `slug` identifies a limited partner or a fund.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 6, 2026

addedInput schema / properties / contact

Added value: +{
+  "description": "Optional. The named person at the target you want to be introduced to (max 80 characters), e.g. \"Jane Doe\".",
+  "type": "string"
+}

addedInput schema / properties / context

Added value: +{
+  "description": "Optional. Short note for Michael: what is being raised, how you are connected, timing (max 1000 characters). Used only when a path check is created.",
+  "type": "string"
+}

AddedNov 2, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only declare readOnly=false, idempotent=true, destructive=false; the description goes far beyond by disclosing hand fulfillment, no guaranteed timeline, the two possible outcomes (charged intro vs. free pending_review with charged: false), and the 14-day expiry. It also covers identity requirements (unlinked agent keys are refused before charging) and the exact pricing rule. Nothing here contradicts the annotations — the free re-ask behavior is consistent with idempotentHint=true.

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?

Purpose and precondition are front-loaded, which is good, but the pricing and plan-exclusion material is restated almost verbatim in the trailing paragraph after already being covered mid-description. The result is roughly double the length needed and buries the practical decision rule under repetition.

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?

This is a paid, identity-bound, human-fulfilled mutation with no output schema, so the description must carry billing, prerequisites and failure modes — and it does. An agent has enough to decide whether to call, predict the charge, and know what happens on a repeat or a failed path check.

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 coverage is 100%, so the schema already documents slug, contact, context and target_type, giving a baseline of 3. The description adds a little meaning — context is only used when a path check is created, and identity matters because Michael contacts a person — but it also introduces a distracting "pay exactly quantity times EUR 50" formula referencing a quantity parameter that does not exist in 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?

Opens with a specific verb and resource ("Ask Michael for a warm intro to a fund or an LP") and immediately constrains scope to human-fulfilled requests rather than automated connections. It positions itself against siblings by naming the prerequisite sources (get_fund, search_lps) and the field (michael_network.has_warm_path) that gates the action.

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?

Explicitly states the when: intros are only sellable where Michael's network already has a path, and a target without one yields a free path check instead. It also spells out the repeat-call case (re-asking is free, returns existing status) and the 14-day auto-close, so an agent knows exactly which branch a call will take.

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

All Fund Momentum tools Inspect

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.