Skip to main content
Glama

Get fund profile

get_fund
Read-onlyIdempotent

THEN: get the detailed profile of one fund, using a slug returned by search_funds. COST: free, no API key required. Every response carries a provenance block stating where each field came from (including per-field sources), when it was last verified, and how confident Fund Momentum is in it, plus a last_close block (close type, date, amount and currency as stated, source URL) when Fund Momentum has covered a close of this fund. Also carries michael_network: {has_warm_path: boolean} on EVERY caller, free, unconditional: whether Michael Schneider, Founder of Fund Momentum, may have a direct path to this fund personally. When true: a Pro caller also gets the matched contact's name; everyone else gets a teaser (no content, just confirmation it exists) pointing at request_warm_intro or the fund's own page -- credits, not a subscription, unlock it. Do not guess the slug from a fund's display name; it will usually be wrong and the call is wasted. A near-miss is resolved only when exactly one fund matches, and the result then carries resolved_from; a name matching several funds is listed, not guessed. Cost: free with no key (10 keyless calls per day) or within a plan quota; 1 credit (EUR 0.01) per call on an agent key.

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

Input Schema

NameRequiredDescriptionDefault
slugYesThe slug identifier of a fund, exactly as returned in the `slug` field of search_funds. Call search_funds first rather than guessing: slugs are not derivable from a fund's display name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"The slug identifier of the fund, as returned by search_funds (e.g. 'index-ventures')"New value: +"The slug identifier of a fund, exactly as returned in the `slug` field of search_funds. Call search_funds first rather than guessing: slugs are not derivable from a fund's display name."
  2. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"The slug identifier of the fund"New value: +"The slug identifier of the fund, as returned by search_funds (e.g. 'index-ventures')"
  3. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, but the description goes well beyond that: it documents the provenance block, per-field sources, last_close, the michael_network teaser behavior, and the near-miss resolution rule with resolved_from. It also states the pricing model twice with slightly different framing ("free, no API key required" vs "1 credit (EUR 0.01) per call on an agent key"), leaving the agent to reconcile the two cost statements.

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

Conciseness2/5

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

Front-loaded THEN/COST labels are helpful, but the body is bloated and misordered: monetization detail ("credits, not a subscription, unlock it") and provenance field enumeration crowd out the core call pattern, and cost is restated at both the top and bottom with different specifics. Several sentences do not earn their place for an agent deciding how to call a one-parameter getter.

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 takes on the return-shape burden and does so: provenance, last_close, michael_network, and the teaser-vs-full-contact split by caller tier are all described. Edge cases (near-miss, ambiguous name, guessed slug) and quota limits are covered.

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% for the single slug parameter, so the schema carries the baseline. The description still adds real meaning beyond it: the near-miss resolution contract (resolved_from) and the multiple-match listing behavior tell the agent how a bad-looking slug will be handled rather than just what to pass.

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 ("get the detailed profile of one fund") and immediately pins the identifier source to a slug returned by search_funds, which separates it from siblings get_fund_signals, get_gp_profile and search_funds. An agent can select this tool without opening 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 Guidelines5/5

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

Explicitly sequences the call ("Call search_funds first rather than guessing"), warns that guessing from a display name wastes the call, and routes the warm-intro case to request_warm_intro. When-to-use, prerequisite and adjacent alternative are all named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.