Skip to main content
Glama

SourceGeek

Search previously known candidates

search_rediscovered_talent
Read-only

Search previously known candidates from SourceGeek workspace sheets and merge connector-sourced candidates before external sourcing. Returns the matched candidates as CSV with source, prior status, last contact, match confidence, contact risk, and recommended re-engagement actions as columns. It does not create a sheet. Stores embeddings of the workspace's sheet rows in SourceGeek to reuse in later searches, and the search's results so a sheet saved later can carry each candidate's match reason and history.

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": {
      "roleDescription": "<roleDescription>"
    },
    "name": "search_rediscovered_talent"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoOptional title for the generated rediscovery sheet.
roleDescriptionYesThe current role target, requirements, or search criteria used to match previously known candidates.
externalCandidatesNoCandidates found via connected sources such as Recruitee MCP search, Gmail, Outlook, Slack, Notion, Google Drive, or OneDrive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the return format (CSV with source, prior status, last contact, match confidence, contact risk, recommended action columns) and the non-creation guarantee. It also discloses a persistence side effect (storing sheet-row embeddings and result history), which adds real context but sits somewhat awkwardly against readOnlyHint=true; it reads as internal caching rather than a user-visible write, so this is a clarity gap rather than a contradiction.

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 purpose and scope, then return shape, then side effects. The embedding/history sentence is dense and could be tighter, but every sentence carries information an agent needs.

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?

For a tool with a nested candidate array, CSV output, and no output schema, the description supplies return columns and side effects, which is most of what an agent needs. Minor gaps remain around CSV handling/pagination and the title parameter's actual effect.

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 the baseline is 3. The description adds meaning by framing externalCandidates as connector-sourced inputs to be merged and roleDescription as the matching criteria, but it does not explain the title parameter or the interaction between a 'generated rediscovery sheet' title and the stated 'does not create a sheet' behavior.

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 ('Search previously known candidates'), names the data source (SourceGeek workspace sheets), and clarifies the merge of connector-sourced candidates. It also explicitly negates a sibling behavior ('It does not create a sheet'), letting an agent separate this from create_sheet/create_rediscovery_shortlist without opening schemas.

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?

'before external sourcing' gives an implied workflow position, and 'It does not create a sheet' implies a follow-up step exists. However, no alternative tool is named and no explicit when-not/exclusion is stated, so routing between this and the shortlist-creation siblings is left to inference.

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