Skip to main content
Glama

Mode VC Chart: Gemini Leaderboard Ranking: Google's Days at #1

SEC Filings Linked to a VC Firm

get_firm_filings
Read-onlyIdempotent

For a firm in the Mode VC Investor Atlas, returns Form ADV adviser records matched to it, recent Form D filings that name its partners, and a recent-activity roll-up. Every match carries a tier: "confirmed" matches are the only verified links; "probable" and "possible" are weaker signals and are hidden unless include_weak_matches is true. Returns "dataset not available yet" until Mode VC has loaded the data.

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_firm_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
firmYesAtlas firm slug or name, e.g. "alumni-ventures".
include_weak_matchesNoAlso return probable and possible matches. Default false.

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

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely non-structured behavior: the confirmed/probable/possible tiering, that weaker tiers are suppressed by default, and the 'dataset not available yet' availability state. Return payload shape is left to the output schema, which is acceptable.

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 what is returned, then the tier semantics, then the availability caveat. Every sentence carries information, though the middle tier sentence is dense and could be split for easier parsing.

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?

With only two parameters, an output schema, and full annotation coverage, the description covers what remains: matching semantics and the not-yet-loaded state. It omits behavior for an unknown or non-Atlas firm slug, which is the only notable gap.

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%, so baseline is 3, but the description adds real meaning beyond the schema: it explains what 'probable' and 'possible' matches actually are and that only 'confirmed' constitutes a verified link, which an agent needs before flipping include_weak_matches.

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 precise verb-and-resource pair: it returns Form ADV adviser records, Form D filings naming partners, and an activity roll-up for a firm in the Mode VC Investor Atlas. The scope is narrow enough that an agent can distinguish it from search_investors or get_investor_details without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It establishes the precondition (the firm must be in the Mode VC Investor Atlas) and the gating rule for weak matches via include_weak_matches. It does not name an alternative tool or state when NOT to call it, so it falls short of a 5.

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