Skip to main content
Glama

There's An AI For That

Search companies

search_companies
Read-only

Search and filter public TAAFT companies by name, description, industry, and products. Exact company names rank first.

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

Input Schema

NameRequiredDescriptionDefault
sortNorelevance
limitNo
queryNoOptional keywords for the company name, description, industry, tools, or models.
offsetNo
countryNoTwo-letter country code.
industryNoIndustry name or industry slug.
ai_nativeNo
profitableNo
tool_companyNo
headcount_maxNo
headcount_minNo
model_companyNo
valuation_maxNo
valuation_minNo
total_raised_maxNo
total_raised_minNo

Output Schema

NameRequiredDescriptionDefault
limitYes
totalYes
offsetYes
has_moreYes
companiesYes
next_offsetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed28 schema fields changed
    • addedInput schema / properties / ai_native
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "Two-letter country code.",
      +  "type": "string"
      +}
    • addedInput schema / properties / headcount_max
      Added value: +{
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / headcount_min
      Added value: +{
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / industry
      Added value: +{
      +  "description": "Industry name or industry slug.",
      +  "type": "string"
      +}
    • addedInput schema / properties / model_company
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / profitable
      Added value: +{
      +  "type": "boolean"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"AI company name to search for."New value: +"Optional keywords for the company name, description, industry, tools, or models."
    • addedInput schema / properties / sort
      Added value: +{
      +  "default": "relevance",
      +  "enum": [
      +    "relevance",
      +    "latest",
      +    "most-raised",
      +    "valuation",
      +    "headcount"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / tool_company
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / total_raised_max
      Added value: +{
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / total_raised_min
      Added value: +{
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / valuation_max
      Added value: +{
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / valuation_min
      Added value: +{
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "query"
      -]
    • addedOutput schema / properties / companies / items / properties / country
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / companies / items / properties / headcount
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / companies / items / properties / industry
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / companies / items / properties / total_raised
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / companies / items / properties / valuation
      Added value: +{
      +  "type": "integer"
      +}
    • changedOutput schema / properties / companies / items / required
      Previous value: -[
      -  "id",
      -  "entity_type",
      -  "name",
      -  "slug",
      -  "url"
      -]New value: +[
      +  "id",
      +  "entity_type",
      +  "name",
      +  "slug",
      +  "url",
      +  "description",
      +  "country",
      +  "industry",
      +  "headcount",
      +  "total_raised",
      +  "valuation"
      +]
    • addedOutput schema / properties / has_more
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / limit
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / next_offset
      Added value: +{
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / offset
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / total
      Added value: +{
      +  "type": "integer"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "companies"
      -]New value: +[
      +  "companies",
      +  "total",
      +  "offset",
      +  "limit",
      +  "has_more",
      +  "next_offset"
      +]
  2. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds one genuine behavioral fact — exact company-name matches rank first — which is not derivable from the schema. It says nothing about pagination behavior or result size beyond what the schema implies.

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 tight sentences with no filler; the ranking behavior is front-loaded alongside the primary capability. Efficient, though its brevity is partly the cause of the coverage gaps.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present the description needn't explain returns, but for a 16-parameter, 19%-documented tool it is far too thin: no usage routing, no pagination/sort semantics, and most filters unexplained. An agent would likely miss or misuse the numeric-range and boolean filters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 19% across 16 parameters, so the description carries most of the burden, yet it names only four filterable dimensions (name, description, industry, products). Key params like sort, limit/offset, country, ai_native, profitable, and the valuation/headcount/total_raised ranges go undocumented anywhere.

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 ('search and filter') and resource ('public TAAFT companies'), and enumerates the primary searchable fields. It does not differentiate itself from the many sibling search_*/get_* tools, nor from search_organizations, which an agent might reasonably confuse it with.

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

Usage Guidelines2/5

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

No statement of when to use this versus get_company (for a known company) or search_organizations. No exclusions, prerequisites, or routing guidance at all — the agent must infer that this is the discovery path for companies.

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.