Skip to main content
Glama

Caelara Labs Web Intelligence

company_intel_composite

Company intelligence: web metadata + DNS + MX in one call

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

Input Schema

NameRequiredDescriptionDefault
domainYesCompany domain, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It reveals the data sources touched, implying passive read-only lookups, but says nothing about permission requirements, rate limits, latency, or what happens when one of the three sub-lookups fails or returns nothing.

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?

The description is a single front-loaded fragment with zero filler, and the component list comes immediately after the purpose. It borders on too terse for a composite tool, but no sentence is wasted.

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?

For a multi-source aggregation tool with no output schema and no annotations, the description sketches what is collected but not the response shape, partial-failure behavior, or cost. That leaves meaningful gaps, though the component list gives a usable mental model of the output.

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 coverage is 100% for the single 'domain' parameter, which already documents the format with an example. The description adds no additional meaning about input handling (e.g., whether bare domains or full URLs are accepted), so 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 a specific resource (company intelligence) and enumerates the exact data sources bundled: web metadata, DNS, and MX. This distinguishes it from narrower siblings like email_mx_forensics, which covers only one of those three components.

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?

The phrase 'in one call' implies the intended usage pattern—aggregating three lookups rather than calling single-purpose tools—but there is no explicit when-to-use, when-not-to-use, or named alternative. The agent must infer the routing decision from the listed components.

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