Skip to main content
Glama

Mode VC Chart: Best AI Model vs. Most Popular AI Chatbot

Search the Mode VC Investor Atlas

search_investors
Read-onlyIdempotent

Searches the Mode VC Investor Atlas, a directory of venture capital firms and their partners compiled from public information (counts are in the response). Filter by firm or partner name, sector, entry stage, and headquarters or location. Stage and check size are as reported by each firm where available; it does not hold portfolio companies or fund performance.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_investors"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum firms to return. Default 10.
queryNoFirm or partner name, e.g. "a16z", "Benchmark", "Marc Andreessen", "Khosla"
stageNoEntry stage the firm reports investing at
sectorNoSector slug, e.g. "ai-and-data", "dev-tools-and-infra", "enterprise-software", "fintech", "crypto", "healthtech", "climate", "consumer"
locationNoGeographic hub, e.g. "california", "new-york", "massachusetts", "toronto", "united-states"

Output Schema

NameRequiredDescriptionDefault
as_ofNo
provenanceYes
source_urlsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "as_of": {
      +      "type": "string"
      +    },
      +    "provenance": {
      +      "properties": {
      +        "as_of": {
      +          "type": "string"
      +        },
      +        "as_of_basis": {
      +          "type": "string"
      +        },
      +        "sources": {
      +          "items": {
      +            "type": "object"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "as_of",
      +        "as_of_basis",
      +        "sources"
      +      ],
      +      "type": "object"
      +    },
      +    "source_urls": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "provenance"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety bar is low. The description still adds real context: the catalog is compiled from public information, result counts appear in the response, and stage/check-size values are self-reported and only present "where available" — a meaningful data-quality caveat an agent can't get from annotations.

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?

Two sentences, front-loaded with the identity of the resource followed by the coverage caveat. Nothing is redundant or filler; only the closing check-size remark is slightly tangential to what the tool actually accepts.

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?

Five optional parameters with an enum, full schema descriptions, and an output schema mean the structured fields carry the mechanics. The description covers the remaining gaps an agent needs — data provenance, self-reported fields, missing portfolio/fund-performance data, and counts in the response.

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 baseline is 3. The description restates the filter axes (firm/partner name, sector, entry stage, headquarters/location) that the schema already documents with examples, and its mention of "check size" does not correspond to any parameter, so it adds no new parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Searches the Mode VC Investor Atlas, a directory of venture capital firms and their partners") and scopes the data source as publicly compiled. It implies a distinction from get_investor_details by being a directory search, but never names a sibling, so differentiation is left to inference.

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?

Usage is implied through the enumerated filter dimensions and one exclusion ("does not hold portfolio companies or fund performance"), which usefully routes agents away from this tool for due-diligence data. However, it never says when to prefer this over get_investor_details or apply_to_mode_vc, nor states prerequisites, so guidance stops short of explicit when/when-not.

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.

Resources