Skip to main content
Glama

urlhaus_lookup

Look up a host, domain, or URL in abuse.ch URLhaus to check whether it is associated with malware or abuse indicators.

Instructions

Look up a host/domain/URL in abuse.ch URLhaus (requires URLHAUS_AUTH_KEY).

abuse.ch now requires a free Auth-Key from auth.abuse.ch; without it this tool returns a clear needs_key result instead of a cryptic 401.

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": {
      "target": "<target>"
    },
    "name": "urlhaus_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does add real behavioral detail: an auth key from auth.abuse.ch is required, and the tool degrades to a clear "needs_key" result rather than a 401. It still does not describe what a successful lookup returns, whether results are cached, or any rate limits, which leaves gaps for a no-annotation tool.

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 one-line purpose statement is front-loaded and the auth note follows as supporting context; nothing is padded. The URLHAUS_AUTH_KEY requirement appears twice (once parenthetically, once in the explanation), which is a minor redundancy.

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

Completeness4/5

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

For a one-parameter, read-only lookup with no output schema, the description covers the essential operational facts: what it queries, what the target accepts, and what happens without credentials. It would be complete at a 5 if it sketched the shape of a successful result, since no output schema exists to do that work.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter "target" has 0% schema description coverage, so the description must compensate — and it does by enumerating the accepted input forms (host, domain, URL), which the schema does not say. It omits format details such as whether an IP or scheme-prefixed URL is valid, keeping it short of a 5.

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 verb and resource ("Look up a host/domain/URL in abuse.ch URLhaus") and identifies the backing service, which implicitly separates it from generic lookups like dns_lookup or asn_lookup. It never explicitly states how it differs from other threat-intel or URL tools, so it stops short of full sibling differentiation.

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 auth precondition and the "needs_key" fallback imply when the tool can be used, but there is no explicit when-to-use guidance, no mention of when to prefer a different lookup, and no exclusions. Usage is left to be inferred from the tool's name and service.

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