Skip to main content
Glama

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

Get One Firm Profile from the Investor Atlas

get_investor_details
Read-onlyIdempotent

Returns one firm from the Investor Atlas: headquarters and locations, website and social links, latest fund as listed, reported entry stages, check size bands (lowest and highest the firm reports) and lead preference where known, sectors, up to 12 partner names (total partner count included), verified public pitch intake_form (when indexed), and a prefilled common_app_url. It does not include portfolio companies or investment theses.

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_or_name": "<slug_or_name>"
    },
    "name": "get_investor_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
slug_or_nameYesFirm slug or name, e.g. "andreessen-horowitz", "sequoia-capital", "accel", "406-ventures"

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds useful content-level caveats — "up to 12 partner names (total partner count included)", "when indexed", "where known" — which tell the agent results can be partial. It does not address error behavior for an unknown slug or whether the name lookup falls back to fuzzy matching.

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?

Purpose is front-loaded in the first clause, followed by a field inventory and a single exclusion sentence — efficient and well ordered. The long enumeration is dense but each item corresponds to a real return field, so little is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the field-by-field inventory in the description is largely redundant with structured data, though it usefully flags partial-data cases. The remaining gap is routing guidance: nothing tells the agent to reach for search_investors or match_vc_intake_forms instead when it lacks a firm identifier.

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 schema itself gives examples of valid slugs. The description contributes nothing about slug_or_name beyond the field name, such as whether a display name is accepted interchangeably or how ambiguous names resolve. Baseline 3 applies since the schema carries the parameter.

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?

The description uses a specific verb and resource ("Returns one firm from the Investor Atlas") and enumerates exactly which fields come back, so the scope is unambiguous. It also states what is excluded (portfolio companies, investment theses). It stops short of naming a sibling like search_investors, so the contrast with discovery tools is only implicit.

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 by "one firm" and the exclusion note, which suggests this is a lookup for a known firm rather than a discovery tool. However, there is no explicit when-to-use statement, no prerequisite about needing a slug or name, and no named alternative for finding firms you cannot name.

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