Skip to main content
Glama

SourceGeek

Find similar company profiles

employee_company_similar_pages
Read-only

List the companies shown as 'people also viewed' next to a company's page (name, username, companyId, industries, staff count) — peers and competitors.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items to return (1-100, default 10). Results beyond the provider's page are not fetched.
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 the safety and external-data profile is covered. The description adds the field list that comes back, but says nothing about pagination, provider coverage limits, or result ordering beyond what the schema's limit parameter already states.

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?

A single front-loaded sentence: the operation and its source ("people also viewed") come first, followed by the returned fields and the peer/competitor framing. Nothing is redundant or padding.

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 only two fully documented parameters and no output schema, the description's enumeration of returned fields compensates well for the missing return contract. What remains thin is routing guidance against the many sibling company/profile tools, which the definition does not address.

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%, so both companyUsernameOrUrl (vanity name or URL) and limit (1-100, default 10, no fetching beyond the provider page) are fully documented in the schema. The description adds no parameter-level meaning beyond that, which is the expected baseline here.

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?

The description gives a specific verb and resource ("List the companies shown as 'people also viewed'") and names the returned fields, so an agent can tell it returns company profiles rather than people profiles. It stops short of explicitly contrasting itself with close siblings such as employee_similar_profiles or employee_company_details.

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?

"Peers and competitors" implies the discovery/comparison use case, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative for fetching a single company's full details or for keyword search. The agent must infer routing from sibling names alone.

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