Skip to main content
Glama

SourceGeek

Search companies

fast_search_companies
Read-only

Search CoreSignal for companies using a natural language query. Use this for finding companies by industry, headcount, location, funding, growth signals, or keywords. Sorting can be requested inside the query (supported fields: employees_count, last_funding_amount, followers_count, active_job_postings_count, num_news_articles, last_updated). Returns the matched companies as CSV (Name, Industry, Size, Employees, HQ Country, Website and company page URL) plus a suggested title — it does not create a sheet. Spends the workspace's credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "fast_search_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRequested number of companies to return (1-20). Defaults to 10 when omitted. The data source returns at most 20 results per search.
queryYesNatural language search query, e.g. 'B2B SaaS companies in Amsterdam with 50-500 employees, sorted by employees_count'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the exact return shape (CSV with Name, Industry, Size, Employees, HQ Country, Website and page URL plus a suggested title), the fact that it does NOT create a sheet, and that it consumes workspace credits. The credit cost and the no-side-effect clarification are exactly the behavioral details an agent needs before invoking a metered search.

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?

Front-loads the core action and use case, then adds sort fields, return format, side-effect clarification, and cost in tight succession. Every sentence carries distinct information; nothing restates the name or annotations.

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

Completeness5/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 takes on the burden of describing return values and does so concretely (CSV columns plus suggested title). It also covers cost and the absence of sheet creation, leaving no material gap for a two-parameter search tool.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by explaining that sorting is requested inside the natural-language query and enumerating the six supported sort fields (employees_count, last_funding_amount, followers_count, active_job_postings_count, num_news_articles, last_updated) — none of which appear in the schema. The limit parameter's 20-result cap is already covered by the schema, so no additional credit there.

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 and resource ('Search CoreSignal for companies') and enumerates the searchable facets: industry, headcount, location, funding, growth signals, keywords. The purpose is unambiguous, but it never distinguishes itself from the sibling 'precision_search_companies' or 'employee_search_companies', so an agent must infer why 'fast' differs from 'precision'.

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

Usage Guidelines4/5

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

Gives a clear usage context ('Use this for finding companies by industry, headcount, location, funding, growth signals, or keywords') that maps well to the natural-language query parameter. It stops short of exclusions or naming an alternative tool for precise/structured filtering, so the when-not-to-use case is left implicit.

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