Skip to main content
Glama

Find a company

find_company
Read-only

Use this when the user names one company and you need to pin down exactly which company it is. Returns its name, website domain, LinkedIn page and logo. Send at least one of name, domain or linkedinUrl; when several are sent only the most precise is looked up (LinkedIn URL, then domain, then name). A bare name resolves to the best-known company of that name, so send a domain for a common name. When nothing matches, the status is not_found: it never guesses. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe company's name.
domainNoThe company's website domain.
linkedinUrlNoThe company's LinkedIn page URL.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A5/5.0
Behavior5/5

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

The description goes far beyond the annotations by detailing the operational behavior, including the priority of lookup (LinkedIn URL > Domain > Name). It also explicitly defines the failure mode as 'not_found: it never guesses,' which is a critical behavioral guarantee.

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?

The definition is highly efficient and well-structured. It front-loads the primary use case and then logically sequences the rules for input necessity, lookup priority, and failure outcomes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the logic involved (priority lookups, ambiguity handling, and cost disclosure), the definition is exceptionally complete. The agent is fully equipped to select and invoke this tool correctly under various input conditions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description provides crucial semantic guidance on the parameters. Specifically, it explains the implications of using a 'bare name' versus providing a domain, which guides the agent's input strategy.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly defines the tool's purpose: to identify and return specific details (name, domain, LinkedIn, logo) for a single company. This purpose is immediately clear and avoids ambiguity regarding its function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides excellent guidelines for usage by stating that at least one input is required. Furthermore, it offers specific advice on how to handle common names versus ambiguous inputs, such as suggesting domains for common names to avoid guessing.

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