Skip to main content
Glama

Search AI companies

search_ai_companies
Read-onlyIdempotent

Find AI startups and companies by topic, sector, country, funding stage, founding year or whether they are hiring. Example: query 'clinical documentation', country 'Australia'. Returns name, one-liner, sector, country, funding facts, website and the presentofai.com page to cite.

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

Input Schema

NameRequiredDescriptionDefault
limitNoResults to return, 1 to 25.
queryNoWords about what the company does, e.g. 'voice agents', 'legal contracts'.
stageNo
cursorNoPass next_cursor from the previous result to get the next page.
sectorNoA sector name; see list_sectors_countries.
countryNoA country name, e.g. 'Germany'.
foundedNoA year (2023) or a range (2021-2024).
hiring_onlyNoOnly companies with open roles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safe, repeatable read behavior is covered. The description adds what fields are returned (name, one-liner, sector, etc.), which is helpful, but doesn't mention pagination behavior beyond the cursor schema or rate limits. With annotations covering safety, a 3 is appropriate as the description adds moderate value.

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 that are front-loaded with the core purpose and then an example. The example adds practical value. Minor verbosity in enumerating filters that are already in the schema, but otherwise efficient.

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?

Given the tool's complexity (8 parameters, no output schema) and the presence of annotations and high schema coverage, the description covers the essential purpose and provides a concrete example. It doesn't discuss pagination (though cursor schema hints at it) or default limit, but these are documented in the schema. Overall complete enough for an agent to use correctly.

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 88%, so the schema already documents most parameters thoroughly. The description's mention of filter dimensions (topic, sector, country, funding stage, founding year, hiring) maps to query, sector, country, stage, founded, and hiring_only, but adds no syntax or format details beyond what the schema provides. Baseline 3 is correct when the schema does the heavy lifting.

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 (''Find'') and resource (''AI startups and companies'') and enumerates filter dimensions (topic, sector, country, funding stage, founding year, hiring). This clearly distinguishes it from siblings like find_ai_jobs (jobs) and get_company (single lookup).

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?

Provides an example query ('clinical documentation', country 'Australia') which implies usage context, but doesn't explicitly state when to use this tool versus get_company or list_sectors_countries. The sector parameter references list_sectors_countries, which is a useful cross-reference, but overall guidance is implicit rather than explicit.

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