Skip to main content
Glama

SourceGeek

Get company profile

employee_company_details
Read-only

Fetch company data by vanity name or company page URL: name, tagline, description, industries, specialities, staff count and range, follower count, headquarters, locations, website, founded year and the numeric companyId.

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": {
      "companyUsernameOrUrl": "<companyUsernameOrUrl>"
    },
    "name": "employee_company_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyUsernameOrUrlYesA company vanity name such as 'google' or a company page URL ending in /company/google.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 safety and external-lookup behavior are covered upstream. The description adds nothing beyond that profile — no note on auth requirements, rate limits, or failure behavior for an unresolvable vanity name. What it does add is a field-level inventory of the response, which substitutes for the absent output schema.

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?

A single front-loaded sentence: the action and input forms come first, the return payload trails. The field enumeration is long but justified given there is no output schema. Minor cost is that it reads as a comma-dump, slightly harder to scan than a grouped listing.

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 one-parameter read tool with no output schema, the description covers the two things an agent needs: how to address the company and what comes back, including the numeric companyId that unlocks id-based siblings. Only the absence of guidance on URL format edge cases or missing-company behavior keeps it from a 5.

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 description coverage is 100% and the single parameter is fully documented with an example, so the baseline is 3. The description earns a point by reframing the parameter as a dual-form key ('vanity name or company page URL') at the top level, reinforcing that a full URL is acceptable rather than just a slug.

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?

Opens with a specific verb+resource ('Fetch company data') and pins down the lookup key ('by vanity name or company page URL'), which implicitly separates it from the id-based sibling. The enumerated field list further disambiguates scope. It stops short of naming the sibling it supersedes, so not a 5.

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?

The accepted input forms (vanity name or /company/ URL) are made explicit, which is the practical when-to-use signal here. There is no statement of when to prefer employee_company_details_by_id, employee_company_by_domain, or employee_search_companies, and no exclusion of ambiguous inputs, so guidance is implied rather than stated.

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