F4 Raise

Get VC firm details

get_vc_firm_details

Read-onlyIdempotent

Use this when the user asks about a specific VC firm by name, or about a firm in a find_vc_firms result. Returns the public profile of one VC firm: name, location, website, a short thesis, the stages it has invested at, check size, sectors, geographies and up to 10 recent public portfolio companies. The firm is a slug from a find_vc_firms result or a name. It returns no contact details and no team names, and it covers only firms that have a public F4 page.

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": {
      "firm": "<firm>"
    },
    "name": "get_vc_firm_details"
  }
}

Input Schema

Name	Required	Description	Default
`firm`	Yes	A firm slug from a find_vc_firms result, or the firm's name.

Output Schema

Name	Required	Description	Default
`firm`	No
`note`	No
`issues`	No
`status`	Yes
`message`	No
`candidates`	No
`retryAfterSeconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the profile is public-only, contains no contact details or team names, and is limited to firms with a public F4 page. It stops short of saying what happens when a firm has no F4 page (empty result vs. error), which keeps it at 4.

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?

Three sentences, front-loaded with the usage trigger before the payload description and the coverage caveat. The middle field-enumeration sentence is somewhat redundant given an output schema exists, but it is compact and readable rather than padded.

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?

For a single-parameter read tool with a full output schema and rich annotations, the description covers trigger, input provenance, returned content, and coverage limitations. Nothing an agent needs to call it correctly is missing.

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% and the single parameter 'firm' is already documented as "a firm slug from a find_vc_firms result, or the firm's name." The description's "The firm is a slug from a find_vc_firms result or a name" restates the schema rather than adding format, case-sensitivity, or disambiguation guidance, so the baseline 3 applies.

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?

"Returns the public profile of one VC firm" is a specific verb+resource, and the sentence enumerates exactly what fields come back (name, location, website, thesis, stages, check size, sectors, geographies, portfolio companies). It is clearly distinguished from the sibling find_vc_firms, which searches rather than retrieves a single firm.

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?

"Use this when the user asks about a specific VC firm by name, or about a firm in a find_vc_firms result" gives an explicit trigger condition and names the sibling that supplies the input slug. It also states a real exclusion — only firms with a public F4 page are covered — so the agent knows when this call will come up empty.

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

All F4 Raise 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.

Resources

Need Help?