Skip to main content
Glama

SourceGeek

Get company employee insights

employee_company_insights
Read-only

Premium company data (5 credits): total headcount with 6m/1y growth and monthly history, headcount and growth by function, monthly hires, job openings by function, median employee tenure and notable recent alumni. Company vanity name or URL required.

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_insights"
  }
}

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.7/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), so the bar is lower; the description adds genuinely new context by disclosing a 5-credit cost and enumerating the payload contents. It does not mention rate limits, auth, or pagination, keeping it short of a 5.

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?

One dense sentence, front-loaded with the cost signal and then the metric inventory — no filler. The metric list is comma-heavy but every item tells the agent what it will receive, which matters given there is no output schema.

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?

With no output schema, the description usefully compensates by listing exactly what is returned (headcount with 6m/1y growth and monthly history, hires, openings, tenure, alumni). The only real gap is the absence of routing guidance against near-sibling company tools.

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?

The trailing 'Company vanity name or URL required' restates the single required parameter, and the schema already documents the format with a concrete example at 100% coverage. The description adds the required-ness emphasis but no format or validation detail beyond the schema.

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 (get) and a well-defined resource: employee/headcount insights for a company, then enumerates the exact metrics returned (headcount, growth, hires, openings, tenure, alumni). This clearly separates it from generic siblings like employee_company_details or employee_company_jobs, though it never names those alternatives explicitly.

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 'Premium company data (5 credits)' framing implies a cost tradeoff versus cheaper sibling tools, but the description never says when to choose this over employee_company_details or employee_company_jobs. Usage is only implied by the returned-metric list.

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