Skip to main content
Glama

SourceGeek

Find company profile by domain

employee_company_by_domain
Read-only

Look up company data by website domain. Returns the company page (name, description, industries, headcount, headquarters, website and companyId), or an error when no company page is mapped to the domain.

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

Input Schema

NameRequiredDescriptionDefault
domainYesWebsite domain such as 'acme.com' (scheme and path are stripped).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), and the description adds real value on top: the exact shape of the success payload (name, description, industries, headcount, headquarters, website, companyId) and the failure mode when no page is mapped to the domain. It does not mention auth or rate limits, but those are not central here.

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?

Two sentences, zero padding, with the lookup behavior front-loaded and the return/error contract following immediately. Every clause carries information.

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 single-parameter, read-only lookup with no output schema, the description supplies the return fields and the error condition, which is what an agent needs to call and interpret it. Only a note on edge cases such as ambiguous or subdomain inputs is missing.

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?

Only one parameter and schema coverage is 100%, with the schema already explaining the 'acme.com' format and that scheme/path are stripped. The description adds no further meaning about the domain parameter, so the baseline applies.

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?

States a specific verb and resource ('Look up company data') plus the exact key ('by website domain'), which implicitly separates it from id-based siblings like employee_company_details_by_id. It stops short of explicitly naming an alternative, so it lands just under the top mark.

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 is only implied: the agent can infer this is the tool for domain-keyed lookups, but there is no explicit when-to-use, when-not-to-use, or pointer to the id/url-based alternatives. Adequate but leaves routing 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