Skip to main content
Glama

Urlhaus Lookup Url

urlhaus_lookup_url
Read-onlyIdempotent

Look up a URL in the URLhaus malware database to check if it is known to host or distribute malware. Returns threat category, status, blacklist status, and tags.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "http://malicious-site.com/payload.exe"
    },
    "name": "urlhaus_lookup_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe full URL to look up (e.g. "http://example.com/malware.exe").

Output Schema

NameRequiredDescriptionDefault
idYesURLhaus ID for this URL
tagsYesAssociated tags for the URL
threatYesThreat category (e.g. 'malware', 'phishing')
blacklistsYesBlacklist detection status by various services
date_addedYesDate when URL was added to database
url_statusYesStatus of the URL (e.g. 'online', 'offline')
query_statusYesStatus of the query (e.g. 'ok', 'no_results')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds that results include threat category, status, blacklist status, and tags, but says nothing about miss behavior (not-found vs clean), rate limits, or upstream data staleness.

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?

Two sentences, front-loaded with the action and data source, then the return fields. No filler, though the return-field sentence is partly redundant given an output schema exists.

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 single-parameter lookup with full schema coverage, an output schema, and rich annotations, the description covers purpose and expected fields adequately. A short note on what a non-match means would close the remaining gap.

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?

Only one parameter and schema coverage is 100%, with the schema already specifying a full URL and giving an example. The description adds no extra syntax constraints such as scheme requirements or handling of queries/fragments, so baseline 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?

States a specific verb and resource ("Look up a URL in the URLhaus malware database") and the exact question it answers (whether the URL is known to host or distribute malware). This distinguishes it clearly from lookups of hosts or payloads and from the recent-events sibling.

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 description implies the check-if-suspicious use case, but gives no explicit when-to-use or when-not-to-use guidance and does not point to the host or payload lookup siblings that cover adjacent indicator types. An agent must infer the routing itself.

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.