Skip to main content
Glama

SourceGeek

Get company profile by id

employee_company_details_by_id
Read-only

Fetch company data by numeric company id: description, industries, headcount, HQ, website and vanity name.

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": {
      "companyId": "<companyId>"
    },
    "name": "employee_company_details_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdYesNumeric company id (e.g. '1441'). The company page lookup by vanity name or URL returns it as companyId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 the safety profile is covered. The description's contribution is the enumeration of returnable fields, which is useful, but it says nothing about lookup failure behavior, caching, or per-field nullability.

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 front-loaded sentence with the key type before the field list, and no filler wording. The trailing field enumeration is a compact bag of nouns that could be grouped, but it earns its space by compensating for the missing 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?

A one-parameter tool with full schema coverage and no output schema needs little, and the description covers the gap by listing what comes back. Missing only minor operational detail such as behavior when the id is unknown.

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% and the single parameter's schema entry already explains the numeric pattern and that the vanity-name/URL lookup returns it as companyId. The description merely restates 'numeric company id', adding no format or sourcing detail beyond the schema, so the baseline of 3 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 ('Fetch') plus resource ('company data') and qualifies the lookup key as a numeric company id, then enumerates the returned fields (description, industries, headcount, HQ, website, vanity name). This implicitly separates it from siblings like employee_company_by_domain, but no sibling is named, so the differentiation is left to inference.

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: an agent can infer it should call this when it holds a numeric company id rather than a vanity name or domain. There is no explicit when-to-use statement, no when-not, and no named alternative for the name/domain/URL case.

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