Skip to main content
Glama

Nightshift agent tools (run by an AI)

Company/domain enrichment

domain_intel
Read-onlyIdempotent

Company/domain enrichment from a domain, URL or email: homepage title and description, social profiles (X, LinkedIn, GitHub, etc.), email provider (Google Workspace, Microsoft 365...), email-sending services from SPF, SaaS vendors from DNS verification records (Atlassian, Stripe, Slack, OpenAI...), website tech stack (CDN, framework, CMS, analytics, chat), DMARC policy, and role contact emails. (Free via MCP, 50 calls/day; unlimited pay-per-call over x402 at $0.004: /api/domain-intel)

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain, URL or email address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds real value beyond that: a 50 calls/day free quota and a priced x402 fallback endpoint, which affects how an agent should plan repeated calls. It omits latency and behavior on unresolvable domains, keeping it from 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?

One front-loaded sentence that leads with the action and then lists outputs; no filler or hedging. The enumeration is long but each item is a distinct returned field, so it earns its space; a bulleted structure would read slightly better.

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?

With no output schema, the description correctly compensates by enumerating what is returned (homepage metadata, socials, email provider, SPF senders, SaaS vendors, tech stack, DMARC, contact emails). Combined with annotation-covered safety semantics and the quota/pricing note, an agent has enough to invoke it 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?

There is a single parameter with 100% schema description coverage, and the schema already states 'Domain, URL or email address' — the description repeats exactly that. Baseline 3 applies since the schema carries the documentation load and no additional format examples or normalization rules are given.

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 opens with a specific verb and resource — 'Company/domain enrichment from a domain, URL or email' — and enumerates the exact data categories returned (social profiles, SPF-derived senders, DMARC, tech stack). An agent knows precisely what this tool produces. It stops short of 5 because it never names an overlapping sibling (dns, email_check, meta, extract) to clarify which one to pick.

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?

Usage is implied rather than stated: giving a domain/URL/email yields enrichment. The free tier (50 calls/day) and x402 pay-per-call fallback do inform the agent about cost/access constraints, which is genuinely useful context. However, there is no explicit when-to-use-this-vs-alternatives guidance and no exclusions.

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.