Skip to main content
Glama

openphish_check

Check a URL or domain against the OpenPhish public phishing feed to identify known phishing threats without an API key.

Instructions

Check a URL or domain against the OpenPhish public phishing feed (keyless).

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": "openphish_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the feed is public and keyless, which is useful authentication context, but it does not explain match semantics, rate limits, feed freshness, or what a successful check returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no wasted words. It delivers the core action, resource, data source, and keyless trait efficiently.

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

Completeness3/5

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

For a one-parameter lookup, the description covers the core action and source, but with no output schema and no annotations it should clarify what the check returns and how results should be interpreted. Those omissions leave meaningful gaps for an agent invoking the tool.

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 0%, so the description must compensate. It usefully states that a URL or domain is accepted, extending beyond the schema's bare 'url' property, but it does not specify expected format, scheme requirements, or examples.

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 states a specific verb and resource: checking a URL or domain against the OpenPhish public phishing feed. It identifies the feed and keyless nature, making the purpose clear, though it does not explicitly distinguish itself from sibling checks like dnsbl_check or breach_check.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies phishing-related use by naming the OpenPhish phishing feed, but provides no explicit when-to-use guidance. It does not say when to choose this over dnsbl_check, breach_check, or other URL/domain checks, nor does it state exclusions.

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