Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_api_company_intel_composite

Retrieve company intelligence in one call by combining web metadata, DNS, and MX records for a domain, helping you verify and profile organizations quickly.

Instructions

[Web Intelligence] Company intelligence: web metadata + DNS + MX in one call Measured p50 12 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://api.caelaralabs.com.

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": "caelara_api_company_intel_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesCompany domain, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does contribute genuine behavioral context that structured fields do not: measured p50 12 ms / p95 15 ms latency with a dated benchmark source, and the upstream host it calls. However, it says nothing about authentication, rate limits, quota/cost, or what happens with an unresolvable or malformed domain, which matters for a network-backed composite.

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?

Three short fragments, front-loaded with the domain category tag then the concrete payload composition. Every clause carries information, though the benchmark citation is verbose relative to its value and appears before any usage guidance.

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

Completeness3/5

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

With no output schema and no annotations, the description must stand in for the response shape. It does enumerate the three result families, which is the key thing an agent needs to judge relevance, but it omits error semantics, whether lookups partially succeed, and any auth/rate-limit context, leaving real gaps for a composite network call.

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 required parameter 'domain' is already documented with an example in the schema. The description adds no formatting rules (bare host vs. URL, subdomain handling, IDN) beyond that, so the schema does the heavy lifting and the baseline 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?

The description names the resource and the exact payload: 'Company intelligence: web metadata + DNS + MX in one call.' That tells an agent precisely which three data families come back, which is more informative than a generic 'get company info'. It stops short of a clean verb phrasing and does not explicitly differentiate itself from the MX-focused sibling, so it lands at 4 rather than 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says when this composite should be chosen over narrower siblings such as email MX forensics or domain trust checks, nor any prerequisite or exclusion. The 'in one call' phrasing hints that it is the bundled option, but the agent must infer that.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools