Skip to main content
Glama

PeopleSearch.im

Search companies

company_search
Read-onlyIdempotent

Search a global company database and get matching companies with industry, size, location and website. Three ways to ask: a company's website ('warmly.ai') returns that one company, the most exact way to identify one; a company's name ('Warmly') returns the companies of that name; a description in plain English ('Series B fintech companies in London with 50-200 employees') returns the companies that fit it. Searching companies uses no credits. It also works before a PeopleSearch.im account is connected: without one it returns up to 3 companies per search, up to 10 searches a day.

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": "company_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA company's website, a company's name, or the companies you want described in plain English.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"The companies you want, in plain English."New value: +"A company's website, a company's name, or the companies you want described in plain English."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, and the description adds information annotations cannot convey: searching consumes no credits, the tool works without a PeopleSearch.im account, and in that unauthenticated state it caps at 3 results per search and 10 searches per day. Those rate and auth details are exactly the behavioral context an agent needs.

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

Conciseness5/5

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

Front-loads the core action and result fields, then the three query modes, then the free/no-account caveats. Each sentence adds new information — no restatement of the title or annotations.

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?

With no output schema, the description compensates by listing the returned attributes. Combined with the query-mode semantics and the unauthenticated result cap, an agent knows what to send, what comes back, and what limits apply.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single param's schema description already names the three forms, so baseline would be 3. The description goes further with worked examples ('warmly.ai', 'Warmly', 'Series B fintech companies in London with 50-200 employees') that clarify the expected string format and which form yields a single exact match.

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 a global company database') plus the returned fields (industry, size, location, website), and enumerates three distinct query modes with concrete examples. An agent can tell this is a broad company-discovery tool rather than the narrower lookup_company or find_company_emails siblings.

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?

Gives clear usage context: three input forms with examples and which is 'most exact' for identifying a single company. It also states cost ('no credits') and the unauthenticated fallback limits, which help an agent decide whether to call it now. It stops short of explicitly saying when to prefer lookup_company or find_company_emails instead, so not a full 5.

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