Skip to main content
Glama

SourceGeek

Search companies (precision)

precision_search_companies
Read-only

Higher-precision CoreSignal company search using the reasoning endpoint. Interprets the natural language query more carefully than the fast search and returns better-matched companies plus an explanation of how it interpreted the query. More expensive and rate-limited (~10/hour, shared with the other precision searches) — use when match quality matters. 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": "precision_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
Behavior4/5

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

Annotations already cover read-only, non-destructive, open-world semantics, yet the description adds substantive behavior: a shared rate limit of roughly 10/hour, workspace credit consumption, and the fact that a query interpretation and suggested title come back with the results. The only omission is what happens on rate-limit exhaustion or whether credits are spent on failed queries.

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?

Front-loaded with the core differentiator and then layered with cost, rate limit, and return shape in a tight sequence with no filler. It is dense and slightly run-on in the returns sentence, but every clause carries decision-relevant information.

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 compensates by enumerating the CSV columns and noting the accompanying interpretation and suggested title. Combined with the rate-limit, credit, and no-sheet-creation notes, an agent has everything needed to call it correctly and set expectations.

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%, with both `query` and `limit` fully documented including length bounds and the 20-result cap, so the description adds no parameter-level detail beyond what is already structured. The baseline 3 applies when the schema carries the burden.

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 and resource (company search via the reasoning endpoint) and immediately contrasts it with 'the fast search', so an agent can distinguish it from fast_search_companies without opening either schema. The added note that it returns an interpretation of the query further pins down what this tool uniquely produces.

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?

Gives an explicit selection rule ('use when match quality matters'), names the cheaper alternative ('the fast search'), and discloses the cost/rate tradeoff (~10/hour shared with other precision searches) that should drive the choice. It also rules out an adjacent action by stating it does not create a sheet, implicitly routing that to a sheet-creation sibling.

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