Skip to main content
Glama

Mode VC Chart: How Long Does the #1 AI Model Stay on Top?

Daily AI Raises from SEC Form D, Scored for Distribution Moat

get_daily_ai_raises
Read-onlyIdempotent

Mode VC's daily read on AI private markets: every new SEC Form D notice from one filing day that public evidence shows is an AI company, scored 1 to 5 with Mode VC's Distribution Moat rubric, with the evidence and reasoning behind each score (the company's own pricing, integrations, customers, docs and product pages when it links them), the status of each distribution lever, atlas partners named in the filing (confirmed and possible kept apart) and the firm's Form ADV private fund assets where that match is confirmed. Filings the evidence cannot settle are listed as unclear, not guessed. A Form D is a self-reported notice, not a closed round. Leave date empty for the latest day.

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": "get_daily_ai_raises"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoForm D filing date, YYYY-MM-DD. Default: latest day available.
limitNoMaximum raises to return. Default 25.
queryNoFilter raises by company name, issuer name, or reasoning keywords.
min_moat_scoreNoOnly raises scoring at least this. Default 1 (all).
include_unclearNoAlso list filings the evidence could not settle. Default true.

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.6/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description adds substantive context beyond them: that unresolved filings are listed as 'unclear' rather than guessed, and the important caveat that a Form D is a self-reported notice, not a closed round. Return contents are enumerated in prose, though output format details are left to the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded, but the body is one sprawling run-on sentence with a long parenthetical, and the caveat about Form D being a notice only arrives at the end. A reader must parse a dense chain of clauses to reconstruct the return contents.

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 read-only, closed-world tool with a full output schema and fully documented parameters, the description covers scope, scoring rubric, evidence basis, and known limitations (unclear filings, self-reported notices). The remaining gap is routing guidance against the closely related sibling tools.

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 all five parameters are already documented, and the description largely restates them (empty date = latest day, unclear filings). It does clarify the semantics of 'unclear' as evidence that could not be settled, which slightly enriches include_unclear. Overall it stays at the baseline because the schema does the heavy lifting.

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 names a specific resource (new SEC Form D notices for AI companies from a single filing day) and a specific operation (score them 1-5 on Mode VC's Distribution Moat rubric, with evidence, lever status, atlas partners and ADV assets). It is far from a tautology. It does not explicitly distinguish itself from the sibling get_distribution_moat_score or get_new_raises, so it stops short of a 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?

It gives one concrete usage rule ('Leave date empty for the latest day') and an implicit scope limit (one filing day at a time). There is no explicit when-to-use versus alternatives such as get_new_raises (raw filings) or get_distribution_moat_score (single-company score), so an agent must infer the routing.

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