Skip to main content
Glama

Mode VC Chart: LangChain Alternatives: Downloads vs. Newer AI SDKs

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, and up to 12 partner names (the total partner count is also given). 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

A3.7/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 needs no restating. The description adds genuine scope context beyond them: the partner list is capped at 12 with a total count supplied, values are "as listed/reported/where known" (signalling possible gaps), and portfolio companies and investment theses are explicitly excluded. That exclusion is the most useful behavioral signal because it prevents the agent from expecting data this tool never returns.

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 core action, then a dense field inventory, then a scope exclusion. Every clause carries information and nothing is repeated. It is list-heavy and long-ish for one sentence, which keeps it just under top marks.

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

Completeness4/5

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

For a single-record read tool with full annotation coverage and an output schema, the description covers scope, contents, and limits well. The remaining gap is what happens when the firm is not found or the name is ambiguous — the "as listed/where known" hedge hints at partial data but not at error behavior.

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?

With one parameter at 100% schema description coverage and worked slug examples in the schema, the schema already carries the semantics. The description adds nothing about the parameter — no note on slug-vs-name resolution, case sensitivity, or behavior on ambiguity — so the baseline 3 applies.

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 opens with a concrete verb+resource ("Returns one firm from the Investor Atlas") and enumerates the exact fields returned: HQ/locations, links, latest fund, entry stages, check size bands, lead preference, sectors, and up to 12 partners with a total count. That is far more specific than the title alone. It stops short of naming the sibling it contrasts with (search_investors), so it lands at 4 rather than 5.

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 only implied: the required slug_or_name plus "one firm" signals a single-record lookup, and the negative clause implies you should go elsewhere for portfolio companies or theses. There is no explicit statement of when to call this versus search_investors (e.g., "use after search_investors to resolve a candidate") and no prerequisites or failure conditions.

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