Skip to main content
Glama

Find people at a company

argorant_company_people
Read-onlyIdempotent

Show how many people Argorant has at one company domain, how many of them have a work email, facts about the company and a few example rows with job titles, names hidden. Use it when the user names one company, rather than putting a domain into free text. For a search across many companies use argorant_count_people or argorant_preview_people. The count is people in Argorant, not the company's total staff. It takes the same people filters as argorant_count_people. It shows no contact details, costs no credits and counts toward the free daily safety limits. More in the docs at https://docs.argorant.com/docs/agents/tools#read-and-preview

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": {
      "domain": "<domain>"
    },
    "name": "argorant_company_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCities by name. A comma means any of them.
limitNoHow many example rows to show (default 5).
stateNoStates or provinces by name or code, such as Texas or TX. A comma means any of them.
titleNoJob titles to find. A comma means any of them. Short forms work both ways, so CFO also finds Chief Financial Officer.
domainYesThe company's website domain, such as linfieldhq.com.
genderNoGender, female or male, based on first name and country. Names used for both women and men are left out. Not available for lending audiences.
radiusNoDistance around the place, between 0.5 and 500.
countryNoCountries, or regions such as Europe, EMEA, DACH, Nordics, Benelux, APAC, LATAM, North America or GCC. A comma means any of them. Regions can overlap. Egypt is in both Middle East and Africa, Mexico is in both North America and LATAM, and Turkey counts as Middle East, not Europe. A person is counted once, even when several of the regions you name include their country.
near_latNoLatitude of the place to search around. Use it with near_lon and radius.
near_lonNoLongitude of the place to search around. Use it with near_lat and radius.
seniorityNoHow senior the person is. Pick one or more.
near_placeNoA place to search around, written out as a city or a postal code, for example Denver, Colorado or 10115 Berlin. Use it with radius.
departmentsNoThe person's department. Pick one or more.
radius_unitNoUnit of the distance, miles (mi, the default) or kilometers (km).
title_matchNoHow a job title must match. words (the default) needs every word as a whole word, so Data does not match Database. exact needs the whole title to be one of the values, so CEO does not match Founder & CEO. contains finds the text anywhere, also inside a word, and is slower.
exclude_cityNoCities to leave out. A comma means any of them.
exclude_stateNoStates or provinces to leave out. A comma means any of them.
exclude_titleNoJob titles to leave out, matched the same way as title. A comma means any of them.
radius_targetNoWhose location counts. any (the default) is where the person is based, or where their company is when their own place is not known. person is only where the person is based, company only where their company is based.
exclude_countryNoCountries or regions to leave out, matched the same way as country. A comma means any of them.
exclude_seniorityNoSeniority levels to leave out. Pick one or more.
exclude_departmentsNoDepartments to leave out. Pick one or more.
exclude_title_matchNoHow the titles to leave out must match, with the same choices. When it is not set, the title choice is used.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description still adds genuinely new behavior: no contact details returned, names masked in example rows, zero credit cost, and consumption of free daily safety limits. It also pre-empts a likely misinterpretation by clarifying the count is Argorant's people, not the company's total headcount.

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-loads the returned payload, then selection guidance, then cost/limit caveats, then a docs link — a logical order with no filler. It is dense but each sentence carries a distinct constraint; only the docs pointer is borderline expendable.

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?

For a 23-parameter read tool with a full output schema and rich annotations, the description covers the remaining burden: what comes back, what is withheld, cost, rate-limit impact, and sibling routing. An agent has everything needed to decide and call correctly.

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% across 23 parameters, so the schema already carries full per-parameter meaning including comma-list syntax and title_match modes. The description only adds a cross-reference ("takes the same people filters as argorant_count_people"), which is useful for transfer but not new semantics. Baseline 3 is appropriate.

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 plus the exact payload: how many people at one company domain, how many with a work email, company facts, and a few example rows with job titles and hidden names. It explicitly distinguishes itself from argorant_count_people and argorant_preview_people, so an agent can pick it without opening a schema.

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 positive trigger ("when the user names one company, rather than putting a domain into free text") and names the two alternatives with the condition that selects them (searching across many companies). Nothing about tool selection 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.