Skip to main content
Glama
Sign In
Harris HawkEye MCP

Harris HawkEye MCP

by legionultramax
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

lookup_lots_domain

Check if a domain is in the Living Off Trusted Sites (LOTS) database to identify legitimate services abused for C2, exfiltration, or payload hosting. Enrich firewall rules and detect T1102/T1567.

Instructions

Check if a domain is in the LOTS (Living Off Trusted Sites) database — legitimate services abused for C2, exfiltration, or payload hosting. Use for proxy/firewall rule enrichment and T1102/T1567 detection.

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain to check (e.g., "pastebin.com", "ngrok.io", "discord.com")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It clearly states the lookup behavior and explains the LOTS concept, but it does not disclose the return format, whether the match is exact, or any limitations. This is adequate but not rich.

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 description is two sentences with no filler. The primary action is front-loaded, followed by useful context and use cases. Every sentence earns its place.

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 simple single-parameter lookup, the description covers purpose and use cases. However, with no output schema and no annotations, it does not explain what the response will contain or any caveats about domain format or matching behavior.

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?

The schema already provides 100% coverage for the single 'domain' parameter, including examples. The description adds no additional parameter-level meaning, so the baseline of 3 applies.

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 uses a specific verb and resource: 'Check if a domain is in the LOTS database.' It also expands the acronym and explains the threat context, making the tool's purpose unmistakable and distinct from sibling lookup tools like lookup_lolbas or lookup_loldriver.

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

Usage Guidelines4/5

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

The description explicitly states when to use the tool: 'Use for proxy/firewall rule enrichment and T1102/T1567 detection.' This gives clear context, though it does not mention alternatives or when not to use it.

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