Retrieve recently added malware URLs from the URLhaus database to identify current malicious endpoints for threat monitoring and blocklist updates.
Get recent malware URLs added to the URLhaus database.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds only the 'recent additions' framing and says nothing about the time window, result count, pagination, or rate limits, so added value is modest.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single tight sentence that front-loads the verb and resource with zero filler. Nothing is padded or redundant.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no parameters, no output schema, and full annotation coverage, the description is largely sufficient for correct invocation. It could be slightly more complete by noting the recency window or approximate result size, but that is a minor gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is nothing for the description to elaborate; baseline 4 applies. No misleading or missing parameter context exists.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Get') and resource ('recent malware URLs added to the URLhaus database'), so an agent understands exactly what it returns. It doesn't explicitly contrast with the sibling urlhaus_lookup_url, but the 'recent' framing implicitly differentiates a listing from a lookup.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied: 'recent' suggests a feed-style listing versus the lookup sibling, but there is no explicit when-to-use or when-not guidance and no mention of alternatives such as urlhaus_lookup_url for a specific URL.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.