Skip to main content
Glama

SourceGeek

Find people or companies by criteria

find_all_entities
Read-only

Discover and evaluate people or companies against explicit match conditions. Returns verified matches with reasoning when complete; may return a findall id if the time budget is exceeded. Starts a paid run with an external research provider and 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": {
      "entityType": "<entityType>",
      "objective": "<objective>",
      "matchConditions": "<matchConditions>"
    },
    "name": "find_all_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectiveYesNatural language goal for the entity search.
entityTypeYesWhether to find people or companies.
matchLimitNoMaximum verified matches to return (default 25, max 50). Limits above 25 use the core generator and cost several times more credits — only go higher when the user needs a larger list.
matchConditionsYesNamed criteria each candidate must satisfy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

The description discloses behavior the annotations cannot: this starts a paid run against an external research provider and consumes the workspace's credits, and it may return a findall id instead of results when the time budget is exceeded. That cost and partial-completion model is exactly the kind of thing an agent needs before invoking, and it materially qualifies the readOnlyHint=true annotation rather than contradicting it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, no filler, and the core capability is front-loaded. However, the credit/cost warning — the most decision-relevant fact — is buried at the end rather than surfaced alongside the purpose statement.

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?

With no output schema, the description usefully covers return shape (verified matches with reasoning, or a findall id on timeout) and cost, which is the right burden for a paid, long-running search. It leaves the findall id lifecycle unaddressed — the agent is not told how to retrieve results afterward — which is the main residual gap for a tool of this complexity.

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 coverage is 100% and the schema itself already documents objective, entityType, matchLimit (including the credit cost of exceeding 25), and matchConditions, so the description adds no parameter-level meaning beyond it. Baseline 3 applies since the schema does the heavy lifting.

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 first sentence names a specific verb pair (discover, evaluate) and a concrete resource (people or companies) bounded by explicit match conditions, which is far more informative than the title alone. It does not name or contrast any sibling search tool (employee_search_people, precision_search_companies, etc.), so the agent cannot tell from the description alone why this tool beats those.

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?

Usage context is implied rather than stated: the phrase 'explicit match conditions' hints at structured multi-criteria queries, and the credit warning implies this is the heavyweight option, but no when-to-use/when-not-to-use rule or named alternative is given. The agent must infer the boundary with the many other people/company search siblings.

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