Skip to main content
Glama

Venture Atlas

by org.ventureatlas
OverviewDiscussionsAdmin

list_upcoming_milestones

Announced, still-upcoming milestones with target dates across all tracked companies, soonest first. This is the forward-looking view: what each company has committed to next and by when, with the source for the commitment and that company's track record on past announcements. Filter by company or industry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum milestones to return.
companyNoCompany slug to filter by.
industryNoIndustry slug to filter by.
includeUndatedNoInclude milestones whose target has no parseable time signal ("Ongoing"). They sort last.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / industry / enum
      Previous value: -[
-  "rockets",
-  "artificial-intelligence",
-  "space-stations",
-  "orbital-economy",
-  "humanoid-robots",
-  "nuclear-fusion",
-  "electric-vehicles",
-  "satellite-mega-constellations",
-  "autonomous-vehicles",
-  "robotaxis",
-  "nuclear-fission",
-  "evtol",
-  "drone-delivery",
-  "civilian-aircrafts",
-  "defense",
-  "biotech",
-  "semiconductors",
-  "energy-storage",
-  "smartphones",
-  "datacenters"
-]New value: +[
+  "rockets",
+  "artificial-intelligence",
+  "space-stations",
+  "orbital-economy",
+  "humanoid-robots",
+  "nuclear-fusion",
+  "electric-vehicles",
+  "satellite-mega-constellations",
+  "autonomous-vehicles",
+  "robotaxis",
+  "nuclear-fission",
+  "evtol",
+  "drone-delivery",
+  "civilian-aircrafts",
+  "defense",
+  "biotech",
+  "semiconductors",
+  "energy-storage",
+  "smartphones",
+  "datacenters",
+  "big-tech"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / industry / enum
      Previous value: -[
-  "rockets",
-  "artificial-intelligence",
-  "space-stations",
-  "orbital-economy",
-  "humanoid-robots",
-  "nuclear-fusion",
-  "electric-vehicles",
-  "satellite-mega-constellations",
-  "autonomous-vehicles",
-  "robotaxis",
-  "nuclear-fission",
-  "evtol",
-  "drone-delivery",
-  "civilian-aircrafts",
-  "defense",
-  "biotech",
-  "semiconductors",
-  "energy-storage",
-  "datacenters"
-]New value: +[
+  "rockets",
+  "artificial-intelligence",
+  "space-stations",
+  "orbital-economy",
+  "humanoid-robots",
+  "nuclear-fusion",
+  "electric-vehicles",
+  "satellite-mega-constellations",
+  "autonomous-vehicles",
+  "robotaxis",
+  "nuclear-fission",
+  "evtol",
+  "drone-delivery",
+  "civilian-aircrafts",
+  "defense",
+  "biotech",
+  "semiconductors",
+  "energy-storage",
+  "smartphones",
+  "datacenters"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / industry / enum
      Previous value: -[
-  "rockets",
-  "artificial-intelligence",
-  "space-stations",
-  "orbital-economy",
-  "humanoid-robots",
-  "nuclear-fusion",
-  "electric-vehicles",
-  "satellite-mega-constellations",
-  "autonomous-vehicles",
-  "robotaxis",
-  "nuclear-fission",
-  "evtol",
-  "drone-delivery",
-  "civilian-aircrafts",
-  "defense",
-  "biotech",
-  "semiconductors",
-  "energy-storage"
-]New value: +[
+  "rockets",
+  "artificial-intelligence",
+  "space-stations",
+  "orbital-economy",
+  "humanoid-robots",
+  "nuclear-fusion",
+  "electric-vehicles",
+  "satellite-mega-constellations",
+  "autonomous-vehicles",
+  "robotaxis",
+  "nuclear-fission",
+  "evtol",
+  "drone-delivery",
+  "civilian-aircrafts",
+  "defense",
+  "biotech",
+  "semiconductors",
+  "energy-storage",
+  "datacenters"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / industry / enum
      Previous value: -[
-  "rockets",
-  "artificial-intelligence",
-  "space-stations",
-  "orbital-economy",
-  "humanoid-robots",
-  "nuclear-fusion",
-  "electric-vehicles",
-  "satellite-mega-constellations",
-  "autonomous-vehicles",
-  "nuclear-fission",
-  "evtol",
-  "drone-delivery",
-  "civilian-aircrafts",
-  "defense",
-  "biotech",
-  "semiconductors",
-  "energy-storage"
-]New value: +[
+  "rockets",
+  "artificial-intelligence",
+  "space-stations",
+  "orbital-economy",
+  "humanoid-robots",
+  "nuclear-fusion",
+  "electric-vehicles",
+  "satellite-mega-constellations",
+  "autonomous-vehicles",
+  "robotaxis",
+  "nuclear-fission",
+  "evtol",
+  "drone-delivery",
+  "civilian-aircrafts",
+  "defense",
+  "biotech",
+  "semiconductors",
+  "energy-storage"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / industry / enum
      Previous value: -[
-  "rockets",
-  "artificial-intelligence",
-  "space-stations",
-  "humanoid-robots",
-  "nuclear-fusion",
-  "electric-vehicles",
-  "satellite-mega-constellations",
-  "autonomous-vehicles",
-  "nuclear-fission",
-  "evtol",
-  "drone-delivery",
-  "civilian-aircrafts",
-  "defense",
-  "biotech",
-  "semiconductors",
-  "energy-storage"
-]New value: +[
+  "rockets",
+  "artificial-intelligence",
+  "space-stations",
+  "orbital-economy",
+  "humanoid-robots",
+  "nuclear-fusion",
+  "electric-vehicles",
+  "satellite-mega-constellations",
+  "autonomous-vehicles",
+  "nuclear-fission",
+  "evtol",
+  "drone-delivery",
+  "civilian-aircrafts",
+  "defense",
+  "biotech",
+  "semiconductors",
+  "energy-storage"
+]
  6. First observed

TDQS

A3.7/5.0
Behavior4/5

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

No annotations, so the description carries the burden and does disclose ordering (soonest first, undated last) and what the result includes (source of commitment plus the company's track record). It stops short of stating read-only semantics, pagination behavior, or any limits.

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 tight sentences, with the primary scope front-loaded and the explanatory 'forward-looking view' framing kept short. Slight redundancy in re-describing the return payload, but nothing wasteful.

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 list tool with full schema coverage and no output schema, the description covers what the tool returns and how results are ordered. Pagination/cap behavior beyond the schema's limit field is not mentioned, a minor gap.

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 description coverage is 100%, so the schema fully documents limit, company, industry, and includeUndated; the baseline is 3. The description only restates that company/industry filtering exists and that undated items sort last.

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+resource with scope ('announced, still-upcoming milestones with target dates across all tracked companies, soonest first') and even previews the payload (source of commitment, company track record). It does not name or distinguish itself against any sibling tool, so it falls short of 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?

The description frames it as 'the forward-looking view,' which implies usage relative to a past/historical view, and notes filtering options. But there is no explicit when-to-use vs. latest_news or the tracker tools, and no exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Venture Atlas toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources