Skip to main content
Glama

Venture Atlas

by org.ventureatlas
OverviewDiscussionsAdmin

search_companies

Search the companies tracked by Venture Atlas by free text and/or industry. Matches company name, summary, product names, CEO, headquarters and industry names. Returns slim records with a trimmed brief; call get_company for the full profile. Omit query to list every company in an industry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum companies to return.
queryNoFree-text query. Omit to list companies without text filtering.
industryNoIndustry slug to filter by.

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

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden; it discloses the searched field set and the response shape (slim records with a trimmed brief), which is real behavioral context for a search tool. It does not cover pagination, case sensitivity, or match ranking, which are the remaining gaps for a no-annotation read tool.

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

Conciseness5/5

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

Three sentences, front-loaded with purpose, then return shape and routing, then the query-omission rule. Every sentence earns its place with no filler.

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 no output schema, the description compensates by describing the return shape and steering to get_company for detail, which is sufficient to call the tool correctly. Pagination and total-count behavior remain unspecified, keeping it just short of complete.

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% – limit, query, and the industry enum all carry their own descriptions, so the schema does the heavy lifting. The description reinforces the query-omission semantics but adds no syntax or format detail beyond the schema; baseline 3 applies.

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 specific verb (search) and resource (companies tracked by Venture Atlas via free text and/or industry), plus the exact fields matched: name, summary, product names, CEO, headquarters, industry. The routing sentence 'call get_company for the full profile' clearly separates it from its sibling.

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

Usage Guidelines5/5

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

Names the alternative (get_company) and the condition that selects it ('full profile' vs the slim records returned here), and explains the query-omission case ('Omit `query` to list every company in an industry'). An agent can decide between this and the sibling without opening either schema.

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