Skip to main content
Glama

SourceGeek

Search company profiles

employee_search_companies
Read-only

Search company data by keyword with optional filters: location ids, industry ids, company-size codes (A=1-10 … H=10,001+ employees) and hasJobs. Returns companies (name, username, companyId, tagline, industries, staff range) plus total and paging.

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": {
      "keyword": "<keyword>"
    },
    "name": "employee_search_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based results page.
limitNoMaximum items to return (1-100, default 10). Results beyond the provider's page are not fetched.
hasJobsNoOnly companies with open job postings.
keywordYesCompany name or keyword, e.g. 'recruitment'.
industryIdsNoIndustry ids.
locationIdsNoGeo ids (numeric part only).
companySizesNoSize buckets: A=1-10 employees, B=11-50 employees, C=51-200 employees, D=201-500 employees, E=501-1,000 employees, F=1,001-5,000 employees, G=5,001-10,000 employees, H=10,001+ employees.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety and external-data profile is covered. The description adds what the result contains (name, username, companyId, tagline, industries, staff range) plus total and paging, which is useful. It says nothing about result caps beyond the schema's limit note, cost, or auth/pagination depth when the provider's page runs out.

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?

Two sentences, front-loaded with the core action and filter set, then the return shape. The size-code enumeration ('A=1-10 … H=10,001+') duplicates the schema verbatim and is the one clearly cuttable clause.

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

Completeness3/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 names the returned fields and mentions total and paging, which is what an agent needs to interpret results. However, for a 7-parameter search tool sitting alongside multiple competing company-search tools, the absence of any guidance on alternatives or filter-combination behavior leaves a real gap.

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 each parameter already documents itself, including the size-bucket meanings. The description largely restates the same filter list and expands the A–H codes that the schema already spells out, adding no new semantics such as how locationIds geo ids are obtained or how filters combine.

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 definition gives a specific verb and resource ('Search company data by keyword') and enumerates the filter dimensions and return fields, so an agent knows exactly what the tool produces. It does not, however, distinguish itself from the sibling company-search tools (fast_search_companies, precision_search_companies), which keeps it out of 5 territory.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance at all. With sibling tools like fast_search_companies and precision_search_companies present, an agent has to guess which company-search entry point is appropriate, and the definition offers no routing signal.

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