Skip to main content
Glama

check_url_safety

Check whether a suspicious web link looks like a phishing or malware URL.

Combines local heuristic checks with live abuse.ch URLhaus lookups (when URLHAUS_AUTH_KEY is set).
Never visits or opens the submitted link.

Args:
    url: The web link to inspect (for example, 'https://example.com/login').

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": {
      "url": "<url>"
    },
    "name": "check_url_safety"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral-disclosure burden. It provides genuinely useful context: it combines local heuristics with live abuse.ch URLhaus lookups that only run when URLHAUS_AUTH_KEY is set, and it states 'Never visits or opens the submitted link,' which is a meaningful safety guarantee. It still omits matters such as rate limits, whether the URL is transmitted to a third party, and whether the operation is read-only versus side-effecting; that omission is worth noting, but it is minor for a lookup 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 description is front-loaded with purpose, follows with behavioral notes, and closes with an Args block. There is almost no wasted wording, though the Args section largely restates the schema and only earns its place because of the example format.

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?

The tool is a single-parameter read-style check, and an output schema exists, so return values do not need to be explained. The description covers the data sources, the conditional dependency on an auth key, and the non-visiting guarantee. The main missing piece is the degradation behavior when URLHAUS_AUTH_KEY is absent, beyond the implicit 'local only'.

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?

Schema description coverage is 0%, so the description must add meaning itself. It does so by identifying the parameter as 'the web link to inspect' and supplying a concrete example format, 'https://example.com/login'. It does not describe validation rules or URL length constraints, but the meaning is unambiguous for a single required string.

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 opens with a specific verb and resource: 'Check whether a suspicious web link looks like a phishing or malware URL.' This clearly identifies the resource as a web link, which separates it from the email- and message-oriented siblings. It does not explicitly name or differentiate itself from any sibling tool, which keeps it below a 5.

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 phrase 'suspicious web link' hints at the intended context, but the description never states when to use this tool versus alternatives such as analyze_scam_message, nor does it state any exclusions. The agent must infer appropriate usage from the word 'suspicious' alone.

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.