Skip to main content
Glama

Company Enrichment

companies
Read-only

Enrich company data by domain. Returns the company's name, description, industry, type, size, founding year, headquarters, employees, estimated revenue range, LinkedIn page, social links, logo and brand colors. Use for business facts about a company. For technical facts about its domain (WHOIS, DNS, SSL, hosting) use site-intel; for a person use profiles. Cost: 3 credits, charged only when a call succeeds.

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": {
      "domain": "<domain>"
    },
    "name": "companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesCompany domain.
company_nameNoOptional name hint.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so safety is covered; the description adds genuinely new context — a stated cost of 3 credits billed only on success. It does not discuss failure modes or partial results (e.g. missing fields for obscure domains), which keeps 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?

Four tight sentences, front-loaded with the operation and its inputs, then routing, then cost. The field enumeration is long but justified because there is no output schema; it could be slightly trimmed without loss.

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?

For a two-parameter enrichment tool with no output schema and permissive annotations, the description covers the input, the returned fields, sibling routing, and billing. An agent has everything needed to decide and call correctly.

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% with only two parameters, so the baseline applies. Beyond schema, the description conveys only that lookups are domain-keyed; it does not explain how the optional company_name hint affects matching or accuracy.

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?

States a specific verb and resource ("Enrich company data by domain") and enumerates the returned facts, so an agent knows exactly what it gets back. The final two sentences explicitly separate it from site-intel and profiles, which are the nearest siblings.

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?

Gives a positive rule ("Use for business facts about a company") and two explicit exclusions with the correct alternatives: site-intel for domain-technical facts, profiles for people. Nothing about selection is left to inference.

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.