Skip to main content
Glama

Urlhaus Get Recent

urlhaus_get_recent
Read-onlyIdempotent

Get a list of recently submitted malware URLs from URLhaus. Useful for monitoring the latest threats.

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": {
      "limit": 50
    },
    "name": "urlhaus_get_recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of recent URLs to return (default 10, max 1000).

Output Schema

NameRequiredDescriptionDefault
urlsYesList of recently submitted malware URLs
countYesNumber of recent URLs returned
query_statusYesStatus of the query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds only that entries are 'recently submitted' — it never defines the recency window, ordering, or whether results are capped/paged, which matters for a feed tool with a max of 1000.

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 short sentences with the operation front-loaded and no redundancy or padding. The second sentence is borderline filler but is brief enough not to cost the reader much.

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-optional-parameter read tool with an output schema, the description covers purpose and a plausible use case, and the schema carries the parameter details. The remaining gap is the undefined recency window, which is the one thing an agent might need to reason about result freshness.

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?

Schema description coverage is 100%; the single `limit` parameter is already documented with default (10) and max (1000). The description adds no additional meaning about what limit counts against or how truncation is signalled, so the baseline of 3 applies.

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?

States a specific verb and resource ('Get a list of recently submitted malware URLs') plus the source system (URLhaus), so the agent knows exactly what is returned. It does not distinguish itself from close siblings such as urlhaus_lookup_url or lookup_payload, leaving the agent to infer that this is the bulk/feed variant.

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?

'Useful for monitoring the latest threats' implies a monitoring/feed use case but gives no explicit when-to-use condition relative to the lookup siblings, and no when-not-to-use or exclusion guidance. The usage signal is present but wholly inferred.

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.