Skip to main content
Glama

SourceGeek

Search candidates

fast_search_leads
Read-only

Search CoreSignal for professionals using a natural language query. Use this for finding recruiting candidates or contacts by title, company, location, seniority, industry, skills, or other professional criteria. Returns the matched candidates as CSV (Name, Title, Company, Location and profile URL) plus a searchId and a suggested title — it does not create a sheet. totalMatches is how many profiles the interpreted query matched before paging: 0 means the criteria as phrased matched nobody, so rephrase (fewer exclusions, broader titles or locations) rather than repeat the same query. Spends the workspace's credits and stores the results in SourceGeek so a sheet saved later can carry the full candidate details.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRequested number of candidates 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. 'VP Engineering at B2B SaaS companies in Amsterdam with 50-500 employees'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior1/5

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

The description contradicts the readOnlyHint annotation by stating that the tool 'Spends the workspace's credits and stores the results in SourceGeek,' which are side effects that modify the environment. This is a direct conflict with readOnlyHint=true.

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?

The description is well-structured and front-loaded with purpose, then usage, return format, and behavioral notes. It is reasonably concise, though some details like the totalMatches explanation are slightly verbose but still valuable.

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 simplicity (2 parameters, no output schema), the description is largely complete: it covers the return format, totalMatches semantics, credit cost, and storage behavior. However, the contradiction with the readOnlyHint annotation undermines the reliability of the stated side effects.

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%, so both parameters (query and limit) are already fully documented in the schema. The description adds no additional semantic details about parameter formats or constraints beyond what the schema provides.

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?

The description states a specific verb and resource: 'Search CoreSignal for professionals using a natural language query' and specifies it finds recruiting candidates or contacts by various criteria. It does not explicitly differentiate itself from siblings like precision_search_leads or fast_search_companies, but the core purpose is clear.

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?

It provides clear usage context: 'Use this for finding recruiting candidates or contacts by title, company, location, seniority, industry, skills, or other professional criteria.' However, it gives no explicit when-not-to-use guidance or named alternatives for similar searches.

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